Skip to content

Commit 136077a

Browse files
committed
Update RFC, MCP, FCP and CFT sections for TWiR-593
1 parent 7c951d5 commit 136077a

File tree

1 file changed

+27
-46
lines changed

1 file changed

+27
-46
lines changed

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

Lines changed: 27 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -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-
6564
An 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. -->
65+
implementation and give feedback, especially before stabilization.
7766

78-
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
79-
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](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.
8777

8878
## Call for Participation; projects and speakers
8979

@@ -139,47 +129,38 @@ Revision range: [4510e86a..2ea33b59](https://perf.rust-lang.org/?start=4510e86a4
139129
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
140130
are the RFCs that were approved for implementation this week:
141131

142-
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
143-
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
144-
<!-- * []() -->
145-
146-
<!--
147-
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
148-
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
149-
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
150-
-->
132+
* *No RFCs were approved this week.*
151133

152134
### Final Comment Period
153135

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

157-
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
158-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
159-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
160-
<!-- * [disposition: ] []() -->
161-
162139
#### Tracking Issues & PRs
163-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
164-
<!-- or if none entered FCP this week, use: -->
165-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
166-
<!-- * [disposition: ] []() -->
167-
168140
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
141+
* [Tracking Issue for slice::array_chunks](https://github.com/rust-lang/rust/issues/74985)
142+
* [Stabilize `cfg_boolean_literals`](https://github.com/rust-lang/rust/pull/138632)
143+
* [Promise `array::from_fn is generated in order of increasing indices`](https://github.com/rust-lang/rust/pull/139099)
144+
* [Stabilize `repr128`](https://github.com/rust-lang/rust/pull/138285)
145+
* [Stabilize `naked_functions`](https://github.com/rust-lang/rust/pull/134213)
146+
* [Fix missing const for inherent pointer `replace` methods](https://github.com/rust-lang/rust/pull/136877)
169147

170-
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
148+
##### [Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
149+
* [core::marker::NoCell in bounds (previously known an [sic] `Freeze`)](https://github.com/rust-lang/rfcs/pull/3633)
171150

172-
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
151+
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
152+
* [Stabilize automatic garbage collection.](https://github.com/rust-lang/cargo/pull/14287)
173153

174-
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
154+
#### Other Areas
155+
* No Items entered Final Comment Period this week for
156+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
157+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc) or
158+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).
175159

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

178162
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
179-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
180-
<!-- or if there are no new or updated RFCs this week, use: -->
181-
<!-- * *No New or Updated RFCs were created this week.* -->
182-
<!-- * [new|updated] []() -->
163+
* [Allow `&&`, `||`, and `!` in `cfg`](https://github.com/rust-lang/rfcs/pull/3796)
183164

184165
## Upcoming Events
185166

0 commit comments

Comments
 (0)