Skip to content

surprises in resolve #6143

Closed
Closed
@graydon

Description

@graydon
Contributor

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)

Activity

catamorphism

catamorphism commented on Aug 12, 2013

@catamorphism
Contributor

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

graydon

graydon commented on Aug 22, 2013

@graydon
ContributorAuthor

accepted for well-defined milestone

alexcrichton

alexcrichton commented on Sep 19, 2013

@alexcrichton
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

catamorphism commented on Sep 26, 2013

@catamorphism
Contributor

De-milestoning inf avor of more specific bugs

huonw

huonw commented on Jan 26, 2014

@huonw
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

A-resolveArea: Name/path resolution done by `rustc_resolve` specificallymetabugIssues about issues themselves ("bugs about bugs")

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @graydon@alexcrichton@pcwalton@catamorphism@huonw

      Issue actions

        surprises in resolve · Issue #6143 · rust-lang/rust