Skip to content

Commit ff5f851

Browse files
committed
Update RFC, MCP, FCP and CFT sections for TWiR-603
1 parent 2a27c1f commit ff5f851

File tree

1 file changed

+34
-42
lines changed

1 file changed

+34
-42
lines changed

draft/2025-06-11-this-week-in-rust.md

Lines changed: 34 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -57,19 +57,19 @@ and just ask the editors to select the category.
5757
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
5858

5959
## Calls for Testing
60-
6160
An important step for RFC implementation is for people to experiment with the
62-
implementation and give feedback, especially before stabilization. The following
63-
RFCs would benefit from user testing before moving forward:
61+
implementation and give feedback, especially before stabilization.
6462

65-
<!-- Calls for Testing go here, use this format:
66-
* [<RFC Topic>](<RFC URL>)
67-
* [Tracking Issue](<Tracking Issue URL>)
68-
* [Testing steps](<Testing Steps URL>)
69-
-->
70-
<!-- or if there are no new or updated RFCs this week, use: -->
71-
<!-- * *No New or Updated RFCs were created this week.* -->
72-
<!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
63+
If you are a feature implementer and would like your RFC to appear in this list, add a
64+
`call-for-testing` label to your RFC along with a comment providing testing instructions and/or
65+
guidance on which aspect(s) of the feature need testing.
66+
67+
* *No calls for testing were issued this week by [Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
68+
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
69+
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
70+
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
71+
72+
[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.
7373

7474
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
7575

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

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

133125
### Final Comment Period
134126

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

138-
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
139-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
140-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
141-
<!-- * [disposition: ] []() -->
142-
143130
#### Tracking Issues & PRs
144-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
145-
<!-- or if none entered FCP this week, use: -->
146-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
147-
<!-- * [disposition: ] []() -->
148-
149131
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
150-
151-
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
152-
153-
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
154-
155-
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
156-
157-
##### [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
132+
* [Tracking Issue for `mixed_integer_ops_unsigned_sub`](https://github.com/rust-lang/rust/issues/126043)
133+
* [Allow storing `format_args!()` in variable](https://github.com/rust-lang/rust/pull/140748)
134+
* [Tracking Issue for File lock API](https://github.com/rust-lang/rust/issues/130994)
135+
* [Sized Hierarchy: Part I](https://github.com/rust-lang/rust/pull/137944)
136+
* [Allow volatile access to non-Rust memory, including address 0](https://github.com/rust-lang/rust/pull/141260)
137+
* [const-eval: allow constants to refer to mutable/external memory, but reject such constants as patterns](https://github.com/rust-lang/rust/pull/140942)
138+
* [Report never type lints in dependencies](https://github.com/rust-lang/rust/pull/141937)
139+
* [builtin dyn impl no guide inference](https://github.com/rust-lang/rust/pull/141352)
140+
* [Change `core::iter::Fuse`'s Default impl to do what its docs say it does](https://github.com/rust-lang/rust/pull/140985)
141+
* [Stabilize derive(CoercePointee)](https://github.com/rust-lang/rust/pull/133820)
142+
* [impl `Default` for `array::IntoIter`](https://github.com/rust-lang/rust/pull/141574)
143+
* [Added `Clone` implementation for `ChunkBy`](https://github.com/rust-lang/rust/pull/138016)
144+
145+
*No Items entered Final Comment Period this week for
146+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
147+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
148+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
149+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period) or
150+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
151+
152+
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
158153

159154
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
160-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
161-
<!-- or if there are no new or updated RFCs this week, use: -->
162-
<!-- * *No New or Updated RFCs were created this week.* -->
163-
<!-- * [new|updated] []() -->
155+
* [new] [RFC: Dedented String Literals](https://github.com/rust-lang/rfcs/pull/3830)
164156

165157
## Upcoming Events
166158

0 commit comments

Comments
 (0)