@@ -54,19 +54,23 @@ and just ask the editors to select the category.
5454[ submit_crate ] : https://users.rust-lang.org/t/crate-of-the-week/2704
5555
5656## Calls for Testing
57-
5857An important step for RFC implementation is for people to experiment with the
5958implementation and give feedback, especially before stabilization. The following
6059RFCs would benefit from user testing before moving forward:
6160
62- <!-- Calls for Testing go here, use this format:
63- * [<RFC Topic>](<RFC URL>)
64- * [Tracking Issue](<Tracking Issue URL>)
65- * [Testing steps](<Testing Steps URL>)
66- -->
67- <!-- or if there are no new or updated RFCs this week, use: -->
68- <!-- * *No New or Updated RFCs were created this week.* -->
69- <!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
61+ ### [ RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing )
62+ * * No calls for testing were issued this week.*
63+
64+ ### [ Rust] ( https://github.com/rust-lang/rust/labels/call-for-testing )
65+ * [ Tracking issue for RFC 3695: Allow boolean literals as cfg predicates] ( https://github.com/rust-lang/rust/issues/131204 )
66+ - [ Testing steps] ( https://github.com/rust-lang/rust/issues/131204#issuecomment-2569314526 )
67+
68+ ### [ Rustup] ( https://github.com/rust-lang/rustup/labels/call-for-testing )
69+ * * No calls for testing were issued this week.*
70+
71+ If you are a feature implementer and would like your RFC to appear on the above list, add the new ` call-for-testing `
72+ label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
73+ need testing.
7074
7175### [ RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing )
7276
@@ -136,47 +140,37 @@ Revision range: [93722f7e..0f1e965f](https://perf.rust-lang.org/?start=93722f7ed
136140Changes to Rust follow the Rust [ RFC (request for comments) process] ( https://github.com/rust-lang/rfcs#rust-rfcs ) . These
137141are the RFCs that were approved for implementation this week:
138142
139- <!-- Approved RFCs go here, use this format: * [Topic](URL) -->
140- <!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
141- <!-- * []() -->
142-
143- <!--
144- ### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
145- <!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
146- <!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
147- -->
143+ * * No RFCs were approved this week.*
148144
149145### Final Comment Period
150146
151147Every week, [ the team] ( https://www.rust-lang.org/team.html ) announces the 'final comment period' for RFCs and key PRs
152148which are reaching a decision. Express your opinions now.
153149
154150#### [ RFCs] ( https://github.com/rust-lang/rfcs/labels/final-comment-period )
155- <!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
156- <!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
157- <!-- * [disposition: ] []() -->
151+ * [ Explicit ABIs in extern] ( https://github.com/rust-lang/rfcs/pull/3722 )
158152
159153#### Tracking Issues & PRs
160- <!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
161- <!-- or if none entered FCP this week, use: -->
162- <!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
163- <!-- * [disposition: ] []() -->
164-
165154##### [ Rust] ( https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
155+ * [ Tracking Issue for ` float_next_up_down ` ] ( https://github.com/rust-lang/rust/issues/91399 )
156+ * [ ` Impl TryFrom<Vec<u8>> for String ` ] ( https://github.com/rust-lang/rust/pull/132268 )
157+ * [ Tracking Issue for anonymous pipe API] ( https://github.com/rust-lang/rust/issues/127154 )
158+ * [ Convert ` struct FromBytesWithNulError ` into enum] ( https://github.com/rust-lang/rust/pull/134143 )
166159
167160##### [ Cargo] ( https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
161+ * [ simplify SourceID Ord/Eq] ( https://github.com/rust-lang/cargo/pull/14980 )
168162
169163##### [ Language Team] ( https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+ )
164+ * * No Language Team Proposals entered Final Comment Period this week.*
170165
171166##### [ Language Reference] ( https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
167+ * * No Language Reference RFCs entered Final Comment Period this week.*
172168
173169##### [ Unsafe Code Guidelines] ( https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
170+ * * No Unsafe Code Guideline Tracking Issues or PRs entered Final Comment Period this week.*
174171
175172#### [ New and Updated RFCs] ( https://github.com/rust-lang/rfcs/pulls )
176- <!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
177- <!-- or if there are no new or updated RFCs this week, use: -->
178- <!-- * *No New or Updated RFCs were created this week.* -->
179- <!-- * [new|updated] []() -->
173+ * * No New or Updated RFCs were created this week.*
180174
181175## Upcoming Events
182176
0 commit comments