Tracking Issue for Rust 2024: Reserve gen keyword #123904
Closed
Description
This is a tracking issue for reserving the gen keyword in Rust 2024 according to:
The feature gate for the issue is #![feature(gen_blocks)].
About tracking issues
Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps
- Reserve the
genkeyword in nightly Rust 2024. - Implement migration lints.
- N/A: Add documentation to the dev guide.
- See the instructions.
- Add documentation to the reference.
- Add documentation to the edition guide.
- Ensure ready for Rust 2024 stabilization.
Unresolved Questions
- Whether we should use some keyword other than
gen. - Whether we should reserve
genas a full keyword or as a contextual one.
Related
- Tracking Issue for
genblocks and functions #117078 - keyword-idents-2024 unable to migrate loop labels or lifetimes #125986
- Implement raw lifetimes and labels (
'r#ident) #126452 - Deny keyword lifetimes pre-expansion #126762
Implementation history
Metadata
Assignees
Labels
Area: The 2024 editionBlocker: Approved by a merged RFC but not yet implemented.Category: An issue tracking the progress of sth. like the implementation of an RFC`gen {}` expressions that produce `Iterator`sStatus: This issue is ready for inclusion in the edition.Relevant to the language team, which will review and decide on the PR/issue.