-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stabilize expr_2021 fragment specifier in all editions #129972
Conversation
r? @fee1-dead rustbot has assigned @fee1-dead. Use |
This comment has been minimized.
This comment has been minimized.
@rustbot labels +I-lang-nominated Thanks for the stabilization PR. Let's nominate to have a look. |
r=me after T-lang deals with this |
This comment has been minimized.
This comment has been minimized.
16206da
to
52e36f8
Compare
@rfcbot fcp merge |
Team member @traviscross has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! cc @rust-lang/lang-advisors: FCP proposed for lang, please feel free to register concerns. |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
@rfcbot reviewed |
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. This will be merged soon. |
…r-errors Stabilize expr_2021 fragment specifier in all editions This is part of the `expr`/`expr_2021` fragment specifier for Edition 2024 (rust-lang#123742). The RFC says we can support expr_2021 in as many editions as is practical, and there's nothing particularly hard about supporting it all the way back to 2015. In editions 2021 and earlier, `expr` and `expr_2021` are synonyms. Their behavior diverges starting in Edition 2024. This is checked by the `expr_2021_inline_const.rs` test. cc `@vincenzopalazzo` `@rust-lang/wg-macros` `@traviscross`
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
52e36f8
to
33b439f
Compare
Small rebased and added the following diff!
Giving a CI run before squash the fixup commit! |
Co-authored-by: Michael Goulet <[email protected]> Co-authored-by: Vincenzo Palazzo <[email protected]>
33b439f
to
c7cd55f
Compare
@bors r=compiler-errors,traviscross |
☀️ Test successful - checks-actions |
Finished benchmarking commit (21aa500): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResults (secondary 6.5%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 769.179s -> 771.18s (0.26%) |
This is part of the
expr
/expr_2021
fragment specifier for Edition 2024 (#123742). The RFC says we can support expr_2021 in as many editions as is practical, and there's nothing particularly hard about supporting it all the way back to 2015.In editions 2021 and earlier,
expr
andexpr_2021
are synonyms. Their behavior diverges starting in Edition 2024. This is checked by theexpr_2021_inline_const.rs
test.cc @vincenzopalazzo @rust-lang/wg-macros @traviscross