-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Tracking Issue for RFC 3501: Edition 2024 #117258
Copy link
Copy link
Closed
Labels
A-edition-2024Area: The 2024 editionArea: The 2024 editionC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFC
Metadata
Metadata
Assignees
Labels
A-edition-2024Area: The 2024 editionArea: The 2024 editionC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFC
Type
Fields
Give feedbackNo fields configured for issues without a type.
This is a meta-tracking issue for the RFC "3501" (rust-lang/rfcs#3501).
Documentation: https://doc.rust-lang.org/nightly/edition-guide/rust-2024/index.htmlArea: The 2024 edition
Issues: A-edition-2024
If you have questions, or are interested in helping with the edition, please join us in the #edition stream on Zulip.
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
precise_capturingsyntax #123432genkeyword #123904!fall back to!#123748Timeline
Items
Related