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 resolves loop collection expr in wrong context #745

Closed
marijnh opened this issue Jul 26, 2011 · 0 comments
Closed

Resolve resolves loop collection expr in wrong context #745

marijnh opened this issue Jul 26, 2011 · 0 comments

Comments

@marijnh
Copy link
Contributor

marijnh commented Jul 26, 2011

You can't currently do something like

for (int x in x) { ... }

because the loop variable will shadow the outer x.

@ghost ghost assigned marijnh Jul 26, 2011
@marijnh marijnh removed their assignment Jun 16, 2014
keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
Updated types of PTRACE requests for musl to be consistent.

For some reason the type of ptrace request constants in musl change for the register based requests. As they are used in the same way and this doesn't mimic musl this has been changed for consistency and ease of use.

First raised in issue rust-lang#744
pdietl pushed a commit to pdietl/rust that referenced this issue Apr 23, 2020
reorganize docs on references
bors pushed a commit to rust-lang-ci/rust that referenced this issue Oct 26, 2020
bors pushed a commit to rust-lang-ci/rust that referenced this issue Oct 26, 2020
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

No branches or pull requests

1 participant