@@ -57,19 +57,18 @@ and just ask the editors to select the category.
5757[ submit_crate ] : https://users.rust-lang.org/t/crate-of-the-week/2704
5858
5959## Calls for Testing
60-
6160An important step for RFC implementation is for people to experiment with the
62- implementation and give feedback, especially before stabilization. The following
63- RFCs would benefit from user testing before moving forward:
61+ implementation and give feedback, especially before stabilization.
6462
65- <!-- Calls for Testing go here, use this format:
66- * [<RFC Topic>](<RFC URL>)
67- * [Tracking Issue](<Tracking Issue URL>)
68- * [Testing steps](<Testing Steps URL>)
69- -->
70- <!-- or if there are no new or updated RFCs this week, use: -->
71- <!-- * *No New or Updated RFCs were created this week.* -->
72- <!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
63+ If you are a feature implementer and would like your RFC to appear in this list, add a
64+ ` call-for-testing ` label to your RFC along with a comment providing testing instructions and/or
65+ guidance on which aspect(s) of the feature need testing.
66+
67+ * No calls for testing were issued this week by [ Rust] ( https://github.com/rust-lang/rust/labels/call-for-testing ) ,
68+ [ Rust language RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing ) or
69+ [ Rustup] ( https://github.com/rust-lang/rustup/labels/call-for-testing ) .*
70+
71+ [ 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.
7372
7473### [ RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing )
7574
@@ -120,47 +119,38 @@ If you are an event organizer hoping to expand the reach of your event, please s
120119Changes to Rust follow the Rust [ RFC (request for comments) process] ( https://github.com/rust-lang/rfcs#rust-rfcs ) . These
121120are the RFCs that were approved for implementation this week:
122121
123- <!-- Approved RFCs go here, use this format: * [Topic](URL) -->
124- <!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
125- <!-- * []() -->
126-
127- <!--
128- ### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
129- <!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
130- <!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
131- -->
122+ * * No RFCs were approved this week.*
132123
133124### Final Comment Period
134125
135126Every week, [ the team] ( https://www.rust-lang.org/team.html ) announces the 'final comment period' for RFCs and key PRs
136127which are reaching a decision. Express your opinions now.
137128
138- #### [ RFCs] ( https://github.com/rust-lang/rfcs/labels/final-comment-period )
139- <!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
140- <!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
141- <!-- * [disposition: ] []() -->
142-
143129#### Tracking Issues & PRs
144- <!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
145- <!-- or if none entered FCP this week, use: -->
146- <!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
147- <!-- * [disposition: ] []() -->
148-
149130##### [ Rust] ( https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
150-
151- ##### [ Cargo] ( https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
152-
153- ##### [ Language Team] ( https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+ )
154-
155- ##### [ Language Reference] ( https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
156-
157- ##### [ Unsafe Code Guidelines] ( https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
131+ * [ Split elided_lifetime_in_paths into tied and untied] ( https://github.com/rust-lang/rust/pull/120808 )
132+ * [ check types of const param defaults] ( https://github.com/rust-lang/rust/pull/139646 )
133+ * [ Stabilize flags for doctest cross compilation] ( https://github.com/rust-lang/rust/pull/137096 )
134+ * [ Do not remove trivial ` SwitchInt ` in analysis MIR] ( https://github.com/rust-lang/rust/pull/139042 )
135+ * [ Implement a lint for implicit autoref of raw pointer dereference - take 2] ( https://github.com/rust-lang/rust/pull/123239 )
136+ * [ Implement ` Default ` for raw pointers] ( https://github.com/rust-lang/rust/pull/139535 )
137+ * [ make abi_unsupported_vector_types a hard error] ( https://github.com/rust-lang/rust/pull/139309 )
138+ * [ Stabilize let chains in the 2024 edition] ( https://github.com/rust-lang/rust/pull/132833 )
139+ * [ Make closure capturing have consistent and correct behaviour around patterns] ( https://github.com/rust-lang/rust/pull/138961 )
140+ * [ Stabilize the ` cell_update ` feature] ( https://github.com/rust-lang/rust/pull/134446 )
141+
142+ #### Other Areas
143+ * * No Items entered Final Comment Period this week for
144+ [ Rust RFCs] ( https://github.com/rust-lang/rfcs/labels/final-comment-period ) ,
145+ [ Cargo] ( https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) ,
146+ [ Language Team] ( https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+ ) ,
147+ [ Language Reference] ( https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) or
148+ [ Unsafe Code Guidelines] ( https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) .
149+
150+ Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
158151
159152#### [ New and Updated RFCs] ( https://github.com/rust-lang/rfcs/pulls )
160- <!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
161- <!-- or if there are no new or updated RFCs this week, use: -->
162- <!-- * *No New or Updated RFCs were created this week.* -->
163- <!-- * [new|updated] []() -->
153+ * * No New or Updated RFCs were created this week.*
164154
165155## Upcoming Events
166156
0 commit comments