@@ -67,29 +67,19 @@ Thanks to [Audun Halland](https://users.rust-lang.org/t/crate-of-the-week/2704/1
67
67
[ submit_crate ] : https://users.rust-lang.org/t/crate-of-the-week/2704
68
68
69
69
## Calls for Testing
70
-
71
70
An important step for RFC implementation is for people to experiment with the
72
- implementation and give feedback, especially before stabilization. The following
73
- RFCs would benefit from user testing before moving forward:
74
-
75
- <!-- Calls for Testing go here, use this format:
76
- * [<RFC Topic>](<RFC URL>)
77
- * [Tracking Issue](<Tracking Issue URL>)
78
- * [Testing steps](<Testing Steps URL>)
79
- -->
80
- <!-- or if there are no new or updated RFCs this week, use: -->
81
- <!-- * *No New or Updated RFCs were created this week.* -->
82
- <!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
71
+ implementation and give feedback, especially before stabilization.
83
72
84
- ### [ RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing )
73
+ If you are a feature implementer
74
+ and would like your RFC to appear in this list, add a ` call-for-testing ` label to your RFC along
75
+ with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
76
+ need testing.
85
77
86
- ### [ Rust] ( https://github.com/rust-lang/rust/labels/call-for-testing )
78
+ * * No calls for testing were issued this week by [ Rust] ( https://github.com/rust-lang/rust/labels/call-for-testing ) ,
79
+ [ Rust language RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing ) or
80
+ [ Rustup] ( https://github.com/rust-lang/rustup/labels/call-for-testing ) .*
87
81
88
- ### [ Rustup] ( https://github.com/rust-lang/rustup/labels/call-for-testing )
89
-
90
- If you are a feature implementer and would like your RFC to appear on the above list, add the new ` call-for-testing `
91
- label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
92
- need testing.
82
+ Let us know if you would like your feature to be tracked as a part of this list.
93
83
94
84
## Call for Participation; projects and speakers
95
85
@@ -201,47 +191,32 @@ Revision range: [ce36a966..f5729cfe](https://perf.rust-lang.org/?start=ce36a966c
201
191
Changes to Rust follow the Rust [ RFC (request for comments) process] ( https://github.com/rust-lang/rfcs#rust-rfcs ) . These
202
192
are the RFCs that were approved for implementation this week:
203
193
204
- <!-- Approved RFCs go here, use this format: * [Topic](URL) -->
205
- <!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
206
- <!-- * []() -->
207
-
208
- <!--
209
- ### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
210
- <!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
211
- <!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
212
- -->
213
-
214
- ### Final Comment Period
215
-
216
- Every week, [ the team] ( https://www.rust-lang.org/team.html ) announces the 'final comment period' for RFCs and key PRs
217
- which are reaching a decision. Express your opinions now.
218
-
219
- #### [ RFCs] ( https://github.com/rust-lang/rfcs/labels/final-comment-period )
220
- <!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
221
- <!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
222
- <!-- * [disposition: ] []() -->
194
+ * [ RFC: project goals for 2025h1] ( https://github.com/rust-lang/rfcs/pull/3764 )
223
195
224
196
#### Tracking Issues & PRs
225
- <!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
226
- <!-- or if none entered FCP this week, use: -->
227
- <!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
228
- <!-- * [disposition: ] []() -->
229
-
230
197
##### [ Rust] ( https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
231
-
232
- ##### [ Cargo] ( https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
233
-
234
- ##### [ Language Team] ( https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+ )
235
-
236
- ##### [ Language Reference] ( https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
237
-
238
- ##### [ Unsafe Code Guidelines] ( https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
198
+ * [ Make ` ptr_cast_add_auto_to_object lint ` into hard error] ( https://github.com/rust-lang/rust/pull/136764 )
199
+ * [ Tracking Issue for ` const_copy_from_slice ` ] ( https://github.com/rust-lang/rust/issues/131415 )
200
+ * [ Tracking Issue for ` const_char_classify ` ] ( https://github.com/rust-lang/rust/issues/132241 )
201
+ * [ Allow ` *const W<dyn A> -> *const dyn A ptr ` cast] ( https://github.com/rust-lang/rust/pull/136127 )
202
+ * [ Fix parsing of ranges after unary operators] ( https://github.com/rust-lang/rust/pull/134900 )
203
+ * [ Tracking issue for ` slice_take ` ] ( https://github.com/rust-lang/rust/issues/62280 )
204
+ * [ Tracking Issue for ` box_uninit_write ` ] ( https://github.com/rust-lang/rust/issues/129397 )
205
+
206
+ #### Other Areas
207
+ * * No Items entered Final Comment Period this week for
208
+ [ Rust RFCs] ( https://github.com/rust-lang/rfcs/labels/final-comment-period ) ,
209
+ [ Cargo] ( https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) ,
210
+ [ Language Team] ( https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+ ) ,
211
+ [ Language Reference] ( https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) or
212
+ [ Unsafe Code Guidelines] ( https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) .*
213
+
214
+ Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
239
215
240
216
#### [ New and Updated RFCs] ( https://github.com/rust-lang/rfcs/pulls )
241
- <!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
242
- <!-- or if there are no new or updated RFCs this week, use: -->
243
- <!-- * *No New or Updated RFCs were created this week.* -->
244
- <!-- * [new|updated] []() -->
217
+ * [ RFC: Add additional ` inline ` intents] ( https://github.com/rust-lang/rfcs/pull/3778 )
218
+ * [ RFC: Add "spaceship" operator.] ( https://github.com/rust-lang/rfcs/pull/3776 )
219
+ * [ Guarantee slice representation] ( https://github.com/rust-lang/rfcs/pull/3775 )
245
220
246
221
## Upcoming Events
247
222
0 commit comments