8000 `import A::B (*)` should copy variables of `A` to global scope? · Issue #264 · nineties/amber · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

import A::B (*) should copy variables of A to global scope? #264

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

Open
nineties opened this issue Apr 15, 2014 · 1 comment
Open

import A::B (*) should copy variables of A to global scope? #264

nineties opened this issue Apr 15, 2014 · 1 comment

Comments

@nineties
Copy link
Owner

No description provided.

nineties pushed a commit that referenced this issue Apr 15, 2014
@nineties
Copy link
Owner Author

I can not find strong reason to do so. I changed the semantics of import A::B (*) so as not to import variables of super modules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant
0