-
Notifications
You must be signed in to change notification settings - Fork 113
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
Suggest global variables #95
base: master
Are you sure you want to change the base?
Conversation
Thanks @styd for taking your time and contributing to DYM! While it is totally reasonable to suggest Let me escalate this conversation to the Ruby core team. I'll get back to you once we come up with a conclusion. |
@yuki24, it's my pleasure. |
We are going to discuss global variables in general at the next Ruby committer meeting. We'll get back to you once we come up with a conclusion, but I feel pretty good about this and we should be able to ship this with Ruby 2.5. |
Hi, @yuki24. How did the Ruby committer meeting go? Have you guys decided anything about the global variables? |
Everything's still in the air and we haven't landed on any conclusion yet. One possibility though is that we may deprecate any symbol global variables like |
Ah, I see. No problem. I already expected that it won't be easy to decide this. |
Any updates on this? How did the committer meeting go? |
Hi, @yuki24.
I'm thinking of adding global variables to suggestions.
Previously:
After this commit:
I also cleaned up the list of global variables so that it doesn't start with special characters or numbers that will never trigger NameError in the first place.