Closed
Description
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)
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
use
can't resolve non-pub parent module throughsuper
#5248match
at all #6449catamorphism commentedon Aug 12, 2013
This appears to have been milestoned without being nominated. Re-nominating to move to milestone 1, well-defined.
graydon commentedon Aug 22, 2013
accepted for well-defined milestone
pub
items withinpriv mod
s #5129alexcrichton commentedon Sep 19, 2013
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 commentedon Sep 26, 2013
De-milestoning inf avor of more specific bugs
huonw commentedon Jan 26, 2014
Triage: only #3352 and #6449 are left open; as such, I'm calling this done.