Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove the deprecated use syntax from the language #2591

Closed
andrewrk opened this issue May 29, 2019 · 3 comments
Closed

remove the deprecated use syntax from the language #2591

andrewrk opened this issue May 29, 2019 · 3 comments
Labels
breaking Implementing this issue could cause existing code to no longer compile or have different behavior. enhancement Solving this issue will likely involve adding new logic or components to the codebase.
Milestone

Comments

@andrewrk
Copy link
Member

Now that #2014 is solved, and zig fmt is auto fixing everybody's code, we can wait 1 release cycle and then delete the use keyword.

@andrewrk andrewrk added enhancement Solving this issue will likely involve adding new logic or components to the codebase. breaking Implementing this issue could cause existing code to no longer compile or have different behavior. labels May 29, 2019
@andrewrk andrewrk added this to the 0.6.0 milestone May 29, 2019
@emekoi
Copy link
Contributor

emekoi commented May 30, 2019

commenting here because the original issue was closed. is there a specific reason that we want to discourage the use of use in code?

@hryx
Copy link
Contributor

hryx commented Jun 9, 2019

usingnamespace (néeuse) is the only language feature which gives the author the power to introduce identifiers into the current scope without a visible declaration. This has invisible side effects, crowds the symbol namespace, and generally seems counter to Zig's clarity-over-brevity virtue. I think its use warrants discouragement and the uglier name is justified.

(I still don't quite grasp why it needs to exist at all (see my unanswered question here), but the issue has been settled and this ticket is for tracking work of an already-accepted change.)

@emekoi
Copy link
Contributor

emekoi commented Jun 10, 2019

my main problem with this is that is makes #1214 seem uglier, which seems to imply that it's going to be not accepted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Implementing this issue could cause existing code to no longer compile or have different behavior. enhancement Solving this issue will likely involve adding new logic or components to the codebase.
Projects
None yet
Development

No branches or pull requests

3 participants