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

Reported path for unresolved named imports is wrong #2123

Closed
brson opened this issue Apr 4, 2012 · 4 comments
Closed

Reported path for unresolved named imports is wrong #2123

brson opened this issue Apr 4, 2012 · 4 comments
Assignees
Labels
A-resolve Area: Path resolution
Milestone

Comments

@brson
Copy link
Contributor

brson commented Apr 4, 2012

// error-pattern:unresolved import: m::f
import x = m::f;

mod m {
}

fn main() {
}
../src/test/compile-fail/unresolved-named-import.rs:2:7: 2:16 error: unresolved import: m::x
../src/test/compile-fail/unresolved-named-import.rs:2 import x = m::f;

The error says we failed to resolve m::x but that is incorrect. We failed to resolve x, we failed to find m::f, and m::x doesn't identify a real thing.

@ghost ghost assigned marijnh Apr 5, 2012
@ghost ghost assigned pcwalton Jun 22, 2012
@catamorphism
Copy link
Contributor

Test after #1935 is done.

@bstrie
Copy link
Contributor

bstrie commented Jul 16, 2012

The example file no longer fails to compile, although shouldn't it? After all, there's still nothing named m::f for it to import.

@catamorphism
Copy link
Contributor

Yes, it should fail to compile, so there's a different bug now.

@catamorphism
Copy link
Contributor

This test passes now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-resolve Area: Path resolution
Projects
None yet
Development

No branches or pull requests

5 participants