From 5d23bd9bcf88cc1663c7457bffa2d83e7eb77a0d Mon Sep 17 00:00:00 2001 From: Brad Gibson Date: Tue, 17 Sep 2024 07:32:19 -0700 Subject: [PATCH] Update RFC, MCP, FCP and CFT sections for TWiR-565 --- draft/2024-09-18-this-week-in-rust.md | 60 ++++++++++++--------------- 1 file changed, 27 insertions(+), 33 deletions(-) diff --git a/draft/2024-09-18-this-week-in-rust.md b/draft/2024-09-18-this-week-in-rust.md index e7a3c4e54..e60cae9f9 100644 --- a/draft/2024-09-18-this-week-in-rust.md +++ b/draft/2024-09-18-this-week-in-rust.md @@ -53,18 +53,19 @@ and just ask the editors to select the category. [submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704 -## [Call for Testing](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) +## 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: - - - +### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) +* *No calls for testing were issued this week.* + +### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing) +* *No calls for testing were issued this week.* + +### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing) +* *No calls for testing were issued this week.* 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 @@ -109,15 +110,7 @@ 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 @@ -125,28 +118,29 @@ Every week, [the team](https://www.rust-lang.org/team.html) announces the 'final which are reaching a decision. Express your opinions now. #### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period) +* *No RFCs entered Final Comment Period this week.* - - - - -#### [Tracking Issues & PRs](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc) +#### Tracking Issues & PRs +##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc) +* *No RFCs entered Final Comment Period this week.* - - - +##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc) +[disposition: merge] [Allow build scripts to report error messages through `cargo::error`](https://github.com/rust-lang/cargo/pull/14435) -### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc) - - - +#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls) +* [new] [RFC: Allow boolean literals as cfg predicates](https://github.com/rust-lang/rfcs/pull/3695) +* [new] [Expose std support via --print](https://github.com/rust-lang/rfcs/pull/3693) +* [new] [RFC: Give users control over `feature unification`](https://github.com/rust-lang/rfcs/pull/3692) +* [new] [Trusted Publishing Support on Crates.io](https://github.com/rust-lang/rfcs/pull/3691) ## Upcoming Events