Tracking Issue for Rust 2024: rustfmt style editions #123799
Assignees
Labels
A-edition-2024
Area: The 2024 edition
A-rustfmt
Area: Rustfmt
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
S-tracking-ready-for-edition
Status: This issue is ready for inclusion in the edition.
T-style
Relevant to the style team, which will review and decide on the PR/issue.
Comments
|
You can also add rust-lang/rustfmt#5933 to the implementation history |
|
note from today's t-style meet: use this one in the edition guide to provide additional/broader context around the style edition impacts, stability policy, etc. so that it doesn't needed to be repeated in other edition sections |
|
@rustbot labels +S-tracking-ready-for-edition We've reviewed, and this item is now ready for Rust 2024. Thanks to @calebcartwright, @ytmimi, and the rest of the rustfmt team for pushing forward this important work and making it ready for the edition. |
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Dec 31, 2024
…r=ytmimi Stabilize `style_edition = "2024"` in-tree This PR stabilizes the `style_edition` flag in rustfmt. **Why am I doing this in-tree?** The beta release cut is imminent (according to forge, on January 3) and this is the most lightweight approach to getting this flag stable on nightly. It's imperative (as far as I can tell -- `@traviscross` can verify or disagree) that we stabilize the `style_edition` flag so that users can control their style edition separately from the edition. I'm happy to move this PR to the rustfmt repo and subsequently prepare a subtree sync if someone on `@rust-lang/rustfmt` believes that we should get this landed on the rustfmt side then synced. If this is the right recourse, I'd like to note that this is still quite time-sensitive. However, I'm happy to dedicate time to get this done if necessary, since I'd really like to un-jeopardize the style edition. Tracking: - rust-lang#123799
github-actions bot
pushed a commit
to rust-lang/miri
that referenced
this issue
Jan 3, 2025
Stabilize `style_edition = "2024"` in-tree This PR stabilizes the `style_edition` flag in rustfmt. **Why am I doing this in-tree?** The beta release cut is imminent (according to forge, on January 3) and this is the most lightweight approach to getting this flag stable on nightly. It's imperative (as far as I can tell -- `@traviscross` can verify or disagree) that we stabilize the `style_edition` flag so that users can control their style edition separately from the edition. I'm happy to move this PR to the rustfmt repo and subsequently prepare a subtree sync if someone on `@rust-lang/rustfmt` believes that we should get this landed on the rustfmt side then synced. If this is the right recourse, I'd like to note that this is still quite time-sensitive. However, I'm happy to dedicate time to get this done if necessary, since I'd really like to un-jeopardize the style edition. Tracking: - rust-lang/rust#123799
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a tracking issue for support for style editions in rustfmt. This is needed to support the Style Edition 2024 which is expected to be released with Rust 2024.
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
style_edition = "2024"in-tree #134929Unresolved Questions
None.
Related
StyleEditionenum andStyleEditionDefaulttrait rustfmt#5933StyleEditionDefaulttrait for all configs rustfmt#5937cc @rust-lang/rustfmt @rust-lang/style @calebcartwright
The text was updated successfully, but these errors were encountered: