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

Resolve doesn't report name conflicts between a module renaming and another module #4033

Closed
catamorphism opened this issue Nov 24, 2012 · 1 comment
Labels
A-resolve Area: Name resolution
Milestone

Comments

@catamorphism
Copy link
Contributor

Test:

extern mod std;

use list = std::map::chained;
use std::list;

fn main() {
    let _x: list::T<int, int> = list::mk();
}

This program should get rejected because I've aliased list to another module, but I'm also using std::list, so list is ambiguous. But the type error I actually get is about list::mk not being resolved (which is to say, std::list::mk not being resolved). The failure should happen earlier.

catamorphism added a commit that referenced this issue Nov 24, 2012
@graydon
Copy link
Contributor

graydon commented Mar 25, 2013

use declarations shadow one another; this is working as intended.

@graydon graydon closed this as completed Mar 25, 2013
RalfJung pushed a commit to RalfJung/rust that referenced this issue Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-resolve Area: Name resolution
Projects
None yet
Development

No branches or pull requests

2 participants