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.

Sign up for GitHub

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

Jump to bottom

Resolve the static region during typechecking, not in the parser #2256

Closed
catamorphism opened this issue Apr 20, 2012 · 1 comment
Closed

Resolve the static region during typechecking, not in the parser #2256

catamorphism opened this issue Apr 20, 2012 · 1 comment
Assignees
@nikomatsakis
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR) A-type-system Area: Type system C-cleanup Category: PRs that clean code up or issues documenting cleanup.
Milestone
old 1.0 milestone

Comments

@catamorphism
Copy link
Contributor

As per a FIXME in the parser (region_from_name): "To be consistent with our type resolution, the static region should probably be resolved during type checking, not in the parser."
@ghost ghost assigned nikomatsakis Apr 20, 2012
@catamorphism
Copy link
Contributor Author

This appears to be no longer an issue, since the FIXME has gone away.

flip1995 pushed a commit to flip1995/rust that referenced this issue Jun 30, 2023
@bors
Auto merge of rust-lang#10909 - Alexendoo:useless-for-in-vec, r=llogiq
e2c655b 
Fix `useless_vec` suggestion in `for _ in vec![..]`

Fixes rust-lang#111034
Fixes rust-lang#2256

changelog: [`useless_vec`]: Fix suggestion in `for _ in vec![..]`
BoxyUwU pushed a commit to BoxyUwU/rust that referenced this issue Feb 25, 2025
@jieyouxu
Merge pull request rust-lang#2256 from torfsen/fix-examples-for-night…
342ced9 
…ly-2025-02-13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nikomatsakis nikomatsakis

Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR) A-type-system Area: Type system C-cleanup Category: PRs that clean code up or issues documenting cleanup.
Projects
None yet
Milestone
old 1.0 milestone
Development

No branches or pull requests
2 participants
@nikomatsakis @catamorphism