Skip to content

resolve: don't speculatively create freevars when resolving #29547

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

Merged
merged 1 commit into from
Nov 4, 2015

Conversation

arielb1
Copy link
Contributor

@arielb1 arielb1 commented Nov 3, 2015

resolve_identifier used to mark a variable as an upvar when used within a closure. However, the function is also used for the "unnecessary qualification" lint, which would mark paths whose last component had the same name as a local as upvars.

Fixes #29522

r? @eddyb

@eddyb
Copy link
Member

eddyb commented Nov 3, 2015

@bors r+

@bors
Copy link
Collaborator

bors commented Nov 3, 2015

📌 Commit ca04855 has been approved by eddyb

@arielb1
Copy link
Contributor Author

arielb1 commented Nov 3, 2015

@bors r=eddyb

@bors
Copy link
Collaborator

bors commented Nov 3, 2015

📌 Commit ca04855 has been approved by eddyb

@bors
Copy link
Collaborator

bors commented Nov 4, 2015

⌛ Testing commit ca04855 with merge c340ea1...

bors added a commit that referenced this pull request Nov 4, 2015
`resolve_identifier` used to mark a variable as an upvar when used within a closure. However, the function is also used for the "unnecessary qualification" lint, which would mark paths whose last component had the same name as a local as upvars.

Fixes #29522 

r? @eddyb
@bors bors merged commit ca04855 into rust-lang:master Nov 4, 2015
@bors bors mentioned this pull request Nov 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect resolution with module paths and closure analysis
3 participants