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

import foo::* sometimes fails to import foo::foo #1873

Closed
marijnh opened this issue Feb 21, 2012 · 2 comments
Closed

import foo::* sometimes fails to import foo::foo #1873

marijnh opened this issue Feb 21, 2012 · 2 comments
Assignees
Labels
A-resolve Area: Name/path resolution done by `rustc_resolve` specifically
Milestone

Comments

@marijnh
Copy link
Contributor

marijnh commented Feb 21, 2012

The file below fails with unresolved name: foo (in the main fn). When moving the import and main out of the extra module, the problem goes away. It also does not happen if fn foo has a name different from its enclosing module.

mod foo {
    fn foo() {}
}
mod blah {
    import foo::*;
    fn main() { foo(); }
}
@ghost ghost assigned marijnh Apr 13, 2012
@ghost ghost assigned pcwalton Jun 22, 2012
@catamorphism
Copy link
Contributor

Test after #1935 is fixed.

@bstrie
Copy link
Contributor

bstrie commented Jul 16, 2012

Can't reproduce with new resolve.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-resolve Area: Name/path resolution done by `rustc_resolve` specifically
Projects
None yet
Development

No branches or pull requests

4 participants