@@ -61,29 +61,19 @@ and just ask the editors to select the category.
6161[ submit_crate ] : https://users.rust-lang.org/t/crate-of-the-week/2704
6262
6363## Calls for Testing
64-
6564An important step for RFC implementation is for people to experiment with the
66- implementation and give feedback, especially before stabilization. The following
67- RFCs would benefit from user testing before moving forward:
68-
69- <!-- Calls for Testing go here, use this format:
70- * [<RFC Topic>](<RFC URL>)
71- * [Tracking Issue](<Tracking Issue URL>)
72- * [Testing steps](<Testing Steps URL>)
73- -->
74- <!-- or if there are no new or updated RFCs this week, use: -->
75- <!-- * *No New or Updated RFCs were created this week.* -->
76- <!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
77-
78- ### [ RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing )
65+ implementation and give feedback, especially before stabilization.
7966
80- ### [ Rust] ( https://github.com/rust-lang/rust/labels/call-for-testing )
67+ If you are a feature implementer
68+ and would like your RFC to appear in this list, add a ` call-for-testing ` label to your RFC along
69+ with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
70+ need testing.
8171
82- ### [ Rustup] ( https://github.com/rust-lang/rustup/labels/call-for-testing )
72+ * * No calls for testing were issued this week by [ Rust] ( https://github.com/rust-lang/rust/labels/call-for-testing ) ,
73+ [ Rust language RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing ) or
74+ [ Rustup] ( https://github.com/rust-lang/rustup/labels/call-for-testing ) .*
8375
84- If you are a feature implementer and would like your RFC to appear on the above list, add the new ` call-for-testing `
85- label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
86- need testing.
76+ Let us know if you would like your feature to be tracked as a part of this list.
8777
8878## Call for Participation; projects and speakers
8979
@@ -132,47 +122,40 @@ Revision range: [f5729cfe..daf59857](https://perf.rust-lang.org/?start=f5729cfed
132122Changes to Rust follow the Rust [ RFC (request for comments) process] ( https://github.com/rust-lang/rfcs#rust-rfcs ) . These
133123are the RFCs that were approved for implementation this week:
134124
135- <!-- Approved RFCs go here, use this format: * [Topic](URL) -->
136- <!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
137- <!-- * []() -->
138-
139- <!--
140- ### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
141- <!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
142- <!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
143- -->
125+ * * No RFCs were approved this week.*
144126
145127### Final Comment Period
146128
147129Every week, [ the team] ( https://www.rust-lang.org/team.html ) announces the 'final comment period' for RFCs and key PRs
148130which are reaching a decision. Express your opinions now.
149131
150- #### [ RFCs] ( https://github.com/rust-lang/rfcs/labels/final-comment-period )
151- <!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
152- <!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
153- <!-- * [disposition: ] []() -->
154-
155132#### Tracking Issues & PRs
156- <!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
157- <!-- or if none entered FCP this week, use: -->
158- <!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
159- <!-- * [disposition: ] []() -->
160-
161133##### [ Rust] ( https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
134+ * [ Denote ` ControlFlow ` as ` #[must_use] ` ] ( https://github.com/rust-lang/rust/pull/137449 )
135+ * [ Turn order dependent trait objects future incompat warning into a hard error] ( https://github.com/rust-lang/rust/pull/136968 )
136+ * [ Stabilize ` const_vec_string_slice ` ] ( https://github.com/rust-lang/rust/pull/137319 )
137+ * [ add a "future" edition] ( https://github.com/rust-lang/rust/pull/137606 )
138+ * [ Tracking Issue for const_sockaddr_setters] ( https://github.com/rust-lang/rust/issues/131714 )
162139
163- ##### [ Cargo] ( https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
140+ ##### [ Rust RFCs] ( https://github.com/rust-lang/rfcs/labels/final-comment-period )
141+ * [ RFC: Deprecate the per-build-target ` edition ` field in ` Cargo.toml ` ] ( https://github.com/rust-lang/rfcs/pull/3772 )
142+ * [ RFC: Demote i686-pc-windows-gnu to Tier 2] ( https://github.com/rust-lang/rfcs/pull/3771 )
164143
165- ##### [ Language Team] ( https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+ )
144+ ##### [ Cargo] ( https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
145+ * [ feat(package): add --exclude-lockfile flag] ( https://github.com/rust-lang/cargo/pull/15234 )
166146
167- ##### [ Language Reference] ( https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
147+ #### Other Areas
148+ * * No Items entered Final Comment Period this week for
149+ [ Language Team] ( https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+ ) ,
150+ [ Language Reference] ( https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) or
151+ [ Unsafe Code Guidelines] ( https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) .
168152
169- ##### [ Unsafe Code Guidelines ] ( https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
153+ Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
170154
171155#### [ New and Updated RFCs] ( https://github.com/rust-lang/rfcs/pulls )
172- <!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
173- <!-- or if there are no new or updated RFCs this week, use: -->
174- <!-- * *No New or Updated RFCs were created this week.* -->
175- <!-- * [new|updated] []() -->
156+ * [ Local Default Bounds to assist ` Forget ` and other ` ?Trait ` .] ( https://github.com/rust-lang/rfcs/pull/3783 )
157+ * [ ` Forget ` marker trait] ( https://github.com/rust-lang/rfcs/pull/3782 )
158+ * [ RFC: Crate changelog field] ( https://github.com/rust-lang/rfcs/pull/3779 )
176159
177160## Upcoming Events
178161
0 commit comments