Skip to content

Commit d3ba6b3

Browse files
Merge pull request #6536 from U007D/master
Update RFC, MCP, FCP and CFT sections for TWiR-594
2 parents c867ff9 + 98f821e commit d3ba6b3

File tree

1 file changed

+26
-50
lines changed

1 file changed

+26
-50
lines changed

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

Lines changed: 26 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -54,29 +54,18 @@ and just ask the editors to select the category.
5454
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
5555

5656
## Calls for Testing
57-
5857
An important step for RFC implementation is for people to experiment with the
59-
implementation and give feedback, especially before stabilization. The following
60-
RFCs would benefit from user testing before moving forward:
61-
62-
<!-- Calls for Testing go here, use this format:
63-
* [<RFC Topic>](<RFC URL>)
64-
* [Tracking Issue](<Tracking Issue URL>)
65-
* [Testing steps](<Testing Steps URL>)
66-
-->
67-
<!-- or if there are no new or updated RFCs this week, use: -->
68-
<!-- * *No New or Updated RFCs were created this week.* -->
69-
<!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
70-
71-
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
58+
implementation and give feedback, especially before stabilization.
7259

73-
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
60+
If you are a feature implementer and would like your RFC to appear in this list, add a
61+
`call-for-testing` label to your RFC along with a comment providing testing instructions and/or
62+
guidance on which aspect(s) of the feature need testing.
7463

75-
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
64+
* *No calls for testing were issued this week by [Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
65+
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) or
66+
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
7667

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

8170
## Call for Participation; projects and speakers
8271

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

120-
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
121-
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
122-
<!-- * []() -->
123-
124-
<!--
125-
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
126-
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
127-
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
128-
-->
109+
* *No RFCs were approved this week.*
129110

130111
### Final Comment Period
131112

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

135-
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
136-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
137-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
138-
<!-- * [disposition: ] []() -->
139-
140116
#### Tracking Issues & PRs
141-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
142-
<!-- or if none entered FCP this week, use: -->
143-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
144-
<!-- * [disposition: ] []() -->
145-
146117
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
147-
148-
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
149-
150-
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
151-
152-
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
153-
154-
##### [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
118+
* [f*::NAN: guarantee that this is a quiet NaN](https://github.com/rust-lang/rust/pull/139483)
119+
* [Stabilize let chains in the 2024 edition](https://github.com/rust-lang/rust/pull/132833)
120+
* [Stabilize the cell_update feature](https://github.com/rust-lang/rust/pull/134446)
121+
* [Stabilize `-Zdwarf-version` as `-Cdwarf-version`](https://github.com/rust-lang/rust/pull/136926)
122+
* [indirect-const-stabilize the `exact_div` intrinsic](https://github.com/rust-lang/rust/pull/139163)
123+
* [Promise `array::from`_fn is generated in order of increasing indices](https://github.com/rust-lang/rust/pull/139099)
124+
125+
#### Other Areas
126+
* *No Items entered Final Comment Period this week for
127+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
128+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
129+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
130+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc) or
131+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
132+
133+
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
155134

156135
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
157-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
158-
<!-- or if there are no new or updated RFCs this week, use: -->
159-
<!-- * *No New or Updated RFCs were created this week.* -->
160-
<!-- * [new|updated] []() -->
136+
* *No New or Updated RFCs were created this week.*
161137

162138
## Upcoming Events
163139

0 commit comments

Comments
 (0)