Tracking Issue for RFC 3501: Edition 2024 · Issue #117258 · rust-lang/rust (original) (raw)

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.html
Issues: A-edition-2024 Area: The 2024 edition

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

• Accept RFC.
  • 2024 Edition rfcs#3501
• Land all lang priority items in Rust 2024.
  • Tracking Issue for Lifetime Capture Rules 2024 (RFC 3498) #117587
    * Tracking issue for precise_capturing syntax #123432
  • Tracking Issue for Rust 2024: Reserve gen keyword #123904
  • Tracking Issue for Rust 2024: Make ! fall back to ! #123748
• 2024-10-11 Go / no go on all items.
• 2024-10-17 Rust 2024 nightly beta.
• 2024-11-28 Stabilize Rust 2024 on master.
• 2025-01-03 Cut Rust 2024 to beta.
• 2025-01-09 Announce Rust 2024 is pending.
• 2025-02-20 Release Rust 2024 with Rust 1.85.

Timeline

Items

• Items that are fully ready for Rust 2024
• Items not yet fully ready for Rust 2024

Related

• Rust 2024 Edition rust-project-goals#117