Skip to content

Commit 90dfee3

Browse files
authored
Update RFC, MCP, FCP and CFT sections for TWiR-597 (#6594)
1 parent 5eab3aa commit 90dfee3

File tree

1 file changed

+25
-46
lines changed

1 file changed

+25
-46
lines changed

draft/2025-04-30-this-week-in-rust.md

Lines changed: 25 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -72,29 +72,19 @@ Thanks to [Robbie VanVossen](https://users.rust-lang.org/t/crate-of-the-week/270
7272
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
7373

7474
## Calls for Testing
75-
7675
An important step for RFC implementation is for people to experiment with the
77-
implementation and give feedback, especially before stabilization. The following
78-
RFCs would benefit from user testing before moving forward:
79-
80-
<!-- Calls for Testing go here, use this format:
81-
* [<RFC Topic>](<RFC URL>)
82-
* [Tracking Issue](<Tracking Issue URL>)
83-
* [Testing steps](<Testing Steps URL>)
84-
-->
85-
<!-- or if there are no new or updated RFCs this week, use: -->
86-
<!-- * *No New or Updated RFCs were created this week.* -->
87-
<!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
76+
implementation and give feedback, especially before stabilization.
8877

89-
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
78+
If you are a feature implementer and would like your RFC to appear in this list, add a
79+
`call-for-testing` label to your RFC along with a comment providing testing instructions and/or
80+
guidance on which aspect(s) of the feature need testing.
9081

91-
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
92-
93-
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
82+
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
83+
* *No calls for testing were issued this week by [Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
84+
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) or
85+
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
9486

95-
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
96-
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
97-
need testing.
87+
[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.
9888

9989
## Call for Participation; projects and speakers
10090

@@ -198,47 +188,36 @@ If you are an event organizer hoping to expand the reach of your event, please s
198188
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
199189
are the RFCs that were approved for implementation this week:
200190

201-
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
202-
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
203-
<!-- * []() -->
204-
205-
<!--
206-
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
207-
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
208-
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
209-
-->
191+
* *No RFCs were approved this week.*
210192

211193
### Final Comment Period
212194

213195
Every week, [the team](https://www.rust-lang.org/team.html) announces the 'final comment period' for RFCs and key PRs
214196
which are reaching a decision. Express your opinions now.
215197

216-
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
217-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
218-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
219-
<!-- * [disposition: ] []() -->
220-
221198
#### Tracking Issues & PRs
222-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
223-
<!-- or if none entered FCP this week, use: -->
224-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
225-
<!-- * [disposition: ] []() -->
226-
227199
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
200+
* [Finalize repeat expr inference behaviour with inferred repeat counts](https://github.com/rust-lang/rust/pull/139635)
201+
* [Partially stabilize LoongArch target features](https://github.com/rust-lang/rust/pull/135015)
202+
* [Unify sidebar buttons to use the same image](https://github.com/rust-lang/rust/pull/140135)
203+
* [de-stabilize bench attribute](https://github.com/rust-lang/rust/pull/134273)
204+
* [Remove some unsized tuple impls now that we don't support unsizing tuples anymore](https://github.com/rust-lang/rust/pull/138340)
228205

229-
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
230-
231-
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
206+
#### Other Areas
232207

233208
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
209+
* [Remove apologies about the Reference](https://github.com/rust-lang/reference/pull/1792)
210+
211+
*No Items entered Final Comment Period this week for
212+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
213+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
214+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+) or
215+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
234216

235-
##### [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
217+
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
236218

237219
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
238-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
239-
<!-- or if there are no new or updated RFCs this week, use: -->
240-
<!-- * *No New or Updated RFCs were created this week.* -->
241-
<!-- * [new|updated] []() -->
220+
* [RFC: naming groups of configuration with cfg_alias](https://github.com/rust-lang/rfcs/pull/3804)
242221

243222
## Upcoming Events
244223

0 commit comments

Comments
 (0)