Skip to content

surprises in resolve #6143

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
graydon opened this issue Apr 30, 2013 · 5 comments
Closed

surprises in resolve #6143

graydon opened this issue Apr 30, 2013 · 5 comments
Assignees
Labels
A-resolve Area: Name/path resolution done by `rustc_resolve` specifically metabug Issues about issues themselves ("bugs about bugs")

Comments

@graydon
Copy link
Contributor

graydon commented Apr 30, 2013

There are a number of ... surprises in resolve, which may be intentional, may not be, or may represent the need to make backwards-incompatible changes. I think they're related, but I'm not sure. I'm collecting them into a metabug here.

The ones I see are #4536 , #5238 , #5248 , #5269 and #3352 (though the last seems less likely related, it provokes a similarly-unclear "shouldn't this work?" feeling from me, and I'm not sure how to classify the bug)

@catamorphism
Copy link
Contributor

This appears to have been milestoned without being nominated. Re-nominating to move to milestone 1, well-defined.

@graydon
Copy link
Contributor Author

graydon commented Aug 22, 2013

accepted for well-defined milestone

@alexcrichton
Copy link
Member

Nominating to de-milestone. I believe the high-priority blocker is #8215, and there are otherwise associated issues, but I don't believe that they should be blockers.

@catamorphism
Copy link
Contributor

De-milestoning inf avor of more specific bugs

@huonw
Copy link
Member

huonw commented Jan 26, 2014

Triage: only #3352 and #6449 are left open; as such, I'm calling this done.

@huonw huonw closed this as completed Jan 26, 2014
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A-resolve Area: Name/path resolution done by `rustc_resolve` specifically metabug Issues about issues themselves ("bugs about bugs")
Projects
None yet
Development

No branches or pull requests

5 participants