@@ -65,29 +65,18 @@ and just ask the editors to select the category.
6565[ submit_crate ] : https://users.rust-lang.org/t/crate-of-the-week/2704
6666
6767## Calls for Testing
68-
6968An important step for RFC implementation is for people to experiment with the
70- implementation and give feedback, especially before stabilization. The following
71- RFCs would benefit from user testing before moving forward:
72-
73- <!-- Calls for Testing go here, use this format:
74- * [<RFC Topic>](<RFC URL>)
75- * [Tracking Issue](<Tracking Issue URL>)
76- * [Testing steps](<Testing Steps URL>)
77- -->
78- <!-- or if there are no new or updated RFCs this week, use: -->
79- <!-- * *No New or Updated RFCs were created this week.* -->
80- <!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
81-
82- ### [ RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing )
69+ implementation and give feedback, especially before stabilization.
8370
84- ### [ Rust] ( https://github.com/rust-lang/rust/labels/call-for-testing )
71+ If you are a feature implementer and would like your RFC to appear in this list, add a
72+ ` call-for-testing ` label to your RFC along with a comment providing testing instructions and/or
73+ guidance on which aspect(s) of the feature need testing.
8574
86- ### [ Rustup] ( https://github.com/rust-lang/rustup/labels/call-for-testing )
75+ * * No calls for testing were issued this week by [ Rust] ( https://github.com/rust-lang/rust/labels/call-for-testing ) ,
76+ [ Rust language RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing ) or
77+ [ Rustup] ( https://github.com/rust-lang/rustup/labels/call-for-testing ) .*
8778
88- If you are a feature implementer and would like your RFC to appear on the above list, add the new ` call-for-testing `
89- label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
90- need testing.
79+ [ 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.
9180
9281## Call for Participation; projects and speakers
9382
@@ -135,47 +124,47 @@ Revision range: [2805e1dc..2fc3deed](https://perf.rust-lang.org/?start=2805e1dc4
135124Changes to Rust follow the Rust [ RFC (request for comments) process] ( https://github.com/rust-lang/rfcs#rust-rfcs ) . These
136125are the RFCs that were approved for implementation this week:
137126
138- <!-- Approved RFCs go here, use this format: * [Topic](URL) -->
139- <!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
140- <!-- * []() -->
141-
142- <!--
143- ### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
144- <!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
145- <!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
146- -->
127+ * * No RFCs were approved this week.*
147128
148129### Final Comment Period
149130
150131Every week, [ the team] ( https://www.rust-lang.org/team.html ) announces the 'final comment period' for RFCs and key PRs
151132which are reaching a decision. Express your opinions now.
152133
153- #### [ RFCs] ( https://github.com/rust-lang/rfcs/labels/final-comment-period )
154- <!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
155- <!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
156- <!-- * [disposition: ] []() -->
157-
158134#### Tracking Issues & PRs
159- <!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
160- <!-- or if none entered FCP this week, use: -->
161- <!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
162- <!-- * [disposition: ] []() -->
163-
164135##### [ Rust] ( https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
165-
166- ##### [ Cargo] ( https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
167-
168- ##### [ Language Team] ( https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+ )
169-
170- ##### [ Language Reference] ( https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
171-
172- ##### [ Unsafe Code Guidelines] ( https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
136+ * [ Add (back) unsupported_calling_conventions lint to reject more invalid calling conventions] ( https://github.com/rust-lang/rust/pull/141435 )
137+ * [ Stabilize ` if let ` guards (` feature(if_let_guard) ` )] ( https://github.com/rust-lang/rust/pull/141295 )
138+ * [ Added ` Clone ` implementation for ` ChunkBy ` ] ( https://github.com/rust-lang/rust/pull/138016 )
139+ * [ Make the ` dangerous_implicit_autorefs ` lint deny-by-default] ( https://github.com/rust-lang/rust/pull/141661 )
140+ * [ Make NonZero< char > possible] ( https://github.com/rust-lang/rust/pull/141001 )
141+ * [ Tracking Issue for nonnull_provenance] ( https://github.com/rust-lang/rust/issues/135243 )
142+ * [ disposition: close] [ Implement operations for Wrapping< T > where Rhs = T] ( https://github.com/rust-lang/rust/pull/140567 )
143+ * [ Split up the ` unknown_or_malformed_diagnostic_attributes ` lint] ( https://github.com/rust-lang/rust/pull/140717 )
144+ * [ Lint on fn pointers comparisons in external macros] ( https://github.com/rust-lang/rust/pull/134536 )
145+ * [ Specify the behavior of ` file! ` ] ( https://github.com/rust-lang/rust/pull/134442 )
146+ * [ Document representation of ` Option<unsafe fn()> ` ] ( https://github.com/rust-lang/rust/pull/141447 )
147+ * [ Stabilize ` feature(generic_arg_infer) ` ] ( https://github.com/rust-lang/rust/pull/141610 )
148+ * [ Allow ` #![doc(test(attr(..)))] ` everywhere] ( https://github.com/rust-lang/rust/pull/140560 )
149+ * [ Tracking Issue for File lock API] ( https://github.com/rust-lang/rust/issues/130994 )
150+ * [ disposition: unspecified] [ Tracking Issue for ` unsigned_signed_diff ` ] ( https://github.com/rust-lang/rust/issues/126041 )
151+ * [ Stabilise ` os_string_pathbuf_leak ` ] ( https://github.com/rust-lang/rust/pull/137992 )
152+
153+ ##### [ Rust RFCs] ( https://github.com/rust-lang/rfcs/labels/final-comment-period )
154+ * [[ RFC] Add ` #[export_ordinal(n)] ` attribute] ( https://github.com/rust-lang/rfcs/pull/3641 )
155+
156+ * No Items entered Final Comment Period this week for
157+ [ Cargo] ( https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) ,
158+ [ Language Reference] ( https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) ,
159+ [ Language Team] ( https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+ ) or
160+ [ Unsafe Code Guidelines] ( https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) .*
161+
162+ Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
173163
174164#### [ New and Updated RFCs] ( https://github.com/rust-lang/rfcs/pulls )
175- <!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
176- <!-- or if there are no new or updated RFCs this week, use: -->
177- <!-- * *No New or Updated RFCs were created this week.* -->
178- <!-- * [new|updated] []() -->
165+ * [ new] [ de-RFC: Remove unsized_locals] ( https://github.com/rust-lang/rfcs/pull/3829 )
166+ * [ new] [ RFC: Procedural macros in same package as app] ( https://github.com/rust-lang/rfcs/pull/3826 )
167+ * [ new] [ RFC: Allow generic impls using local trait bounds] ( https://github.com/rust-lang/rfcs/pull/3821 )
179168
180169## Upcoming Events
181170
0 commit comments