Repository navigation
Tracking Issue for "don't special case diverging blocks" #123747
Description
This is a tracking issue for the change to not special case the type of diverging 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
- Implement in nightly Rust 2024.
- Implement migration lints.
- Add a list against control-flow keywords used with
;at the end of a block (e.g.{ return; }). - Add a FCW for special cased blocks #125793
- Add a list against control-flow keywords used with
- Adjust
rustfmt. - Add documentation to the dev guide.
- See the instructions.
- Add documentation to the reference.
- See the instructions.
- Add documentation to the edition guide.
- Add formatting for new syntax to the style guide.
- See the nightly style procedure.
- Ensure ready for Rust 2024 stabilization.
Unresolved Questions
None.
Related
- Remove semicolon after break/continue/return by default? rustfmt#993
- Implement
trailing_semicolon = "Preserve"rustfmt#6149
Implementation history
- Edition 2024: don't special-case diverging blocks as much #123590
- Add a FCW for special cased blocks #125793
cc @WaffleLapkin @rust-lang/style @rust-lang/rustfmt @calebcartwright
Reacted by Ruby Lazuli
Activity
traviscross commentedon Jun 6, 2024
@rustbot labels -A-edition-2024
As described here:
This isn't going to happen for Rust 2024, and there's no current plan otherwise to change the status quo, so let's remove this from the edition and close the tracking issue.