Tracking Issue for RFC 3593: Reserve unprefixed guarded string literals in Edition 2024

[traviscross]

This is a tracking issue for the RFC 3593: Reserve unprefixed guarded string literals in Edition 2024.

• RFC: Reserve unprefixed guarded string literals in Edition 2024 rfcs#3593

The feature gate for the issue is #![feature(unprefixed_guarded_strings)].

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 the RFC.
  • RFC: Reserve unprefixed guarded string literals in Edition 2024 rfcs#3593
• Implement in nightly Rust 2024.
  • Reserve guarded string literals (RFC 3593) #123951
  • Experiment: Reserve guarded string literal syntax (RFC 3593) on all editions #124605
• Implement migration lints.
  • Reserve guarded string literals (RFC 3593) #123951
• N/A: Add documentation to the dev guide.
  • See the instructions.
• Add documentation to the reference.
  • See the instructions.
  • 2024: Add reserved syntax reference#1652
• Add documentation to the edition guide.
  • 2024: Add reserved syntax edition-guide#326
• Add formatting for new syntax to the style guide.
  • See the nightly style procedure.
  • N/A.
• Ensure ready for Rust 2024 stabilization.

Unresolved Questions

None.

Implementation history

• Reserve guarded string literals (RFC 3593) #123951

cc @pitaj