From 61e1c2561de16eac88c41b7e08f915f914a2bd52 Mon Sep 17 00:00:00 2001 From: Curly Date: Tue, 27 May 2025 06:26:06 -0700 Subject: [PATCH] Update RFC, MCP, FCP and CFT sections for TWiR-601 --- draft/2025-05-28-this-week-in-rust.md | 73 ++++++++++----------------- 1 file changed, 27 insertions(+), 46 deletions(-) diff --git a/draft/2025-05-28-this-week-in-rust.md b/draft/2025-05-28-this-week-in-rust.md index 423182eda..5522c310d 100644 --- a/draft/2025-05-28-this-week-in-rust.md +++ b/draft/2025-05-28-this-week-in-rust.md @@ -57,29 +57,18 @@ and just ask the editors to select the category. [submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704 ## Calls for Testing - An important step for RFC implementation is for people to experiment with the -implementation and give feedback, especially before stabilization. The following -RFCs would benefit from user testing before moving forward: - - - - - +implementation and give feedback, especially before stabilization. -### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) +If you are a feature implementer and would like your RFC to appear in this list, add a +`call-for-testing` label to your RFC along with a comment providing testing instructions and/or +guidance on which aspect(s) of the feature need testing. -### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing) +* *No calls for testing were issued this week by [Rust](https://github.com/rust-lang/rust/labels/call-for-testing), + [Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) or + [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).* -### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing) - -If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing` -label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature -need testing. +[Let us know](https://github.com/rust-lang/this-week-in-rust/issues) if you would like your feature to be tracked as a part of this list. ## Call for Participation; projects and speakers @@ -120,47 +109,39 @@ If you are an event organizer hoping to expand the reach of your event, please s Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These are the RFCs that were approved for implementation this week: - - - - - +* *No RFCs were approved this week.* ### Final Comment Period Every week, [the team](https://www.rust-lang.org/team.html) announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now. -#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period) - - - - #### Tracking Issues & PRs - - - - - ##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc) +* [Allow comparisons between `CStr`, `CString`, and `Cow`.](https://github.com/rust-lang/rust/pull/137268) +* [Tracking Issue for `const_eq_ignore_ascii_case`](https://github.com/rust-lang/rust/issues/131719) +* [Stabilize feature result_flattening](https://github.com/rust-lang/rust/pull/141072) +* [Tracking Issue for `breakpoint` feature (`core::arch::breakpoint`)](https://github.com/rust-lang/rust/issues/133724) +* [Stabilize `sha512`. `sm3` and `sm4` for x86](https://github.com/rust-lang/rust/pull/140767) +* [Stabilize keylocker](https://github.com/rust-lang/rust/pull/140766) +* [terminology: allocated object → allocation](https://github.com/rust-lang/rust/pull/141224) +* [Tracking Issue for `keylocker_x86`](https://github.com/rust-lang/rust/issues/134813) +* [Tracking Issue for `sha512_sm_x86`](https://github.com/rust-lang/rust/issues/126624) ##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc) +* [Use `gix` for `cargo package`](https://github.com/rust-lang/cargo/pull/15534) -##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+) - -##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc) +*No Items entered Final Comment Period this week for +[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period), +[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc), +[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+) or +[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).* -##### [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc) +Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list. #### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls) - - - - +* [new] [RFC: Changes to target_feature attribute](https://github.com/rust-lang/rfcs/pull/3820) +* [new] [RFC: Promote aarch64-pc-windows-msvc to Tier 1](https://github.com/rust-lang/rfcs/pull/3817) ## Upcoming Events