diff options
| author | bors <bors@rust-lang.org> | 2024-12-31 03:05:49 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-12-31 03:05:49 +0000 |
| commit | 80f5a81df9bdb6e11595b0ac8c0bc843786d926b (patch) | |
| tree | 6f7eecc6f678562f7d8a82a9e23af3b0cfcdb01b /compiler/rustc_codegen_llvm/messages.ftl | |
| parent | 4e5fec2f1ea4b1cfecaa14304c9f56de59b344cb (diff) | |
| parent | f694db1e28adbff573c9430d9f6e7d129dc1c5ea (diff) | |
| download | rust-80f5a81df9bdb6e11595b0ac8c0bc843786d926b.tar.gz rust-80f5a81df9bdb6e11595b0ac8c0bc843786d926b.zip | |
Auto merge of #134929 - compiler-errors:style-edition-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: - https://github.com/rust-lang/rust/issues/123799
Diffstat (limited to 'compiler/rustc_codegen_llvm/messages.ftl')
0 files changed, 0 insertions, 0 deletions