Skip to content

Commit 1ee87c0

Browse files
authored
Update RFC, MCP, FCP and CFT sections for TWiR-605 (#6765)
1 parent 6fe17fb commit 1ee87c0

File tree

1 file changed

+25
-39
lines changed

1 file changed

+25
-39
lines changed

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

Lines changed: 25 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -75,19 +75,19 @@ and just ask the editors to select the category.
7575
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
7676

7777
## Calls for Testing
78-
7978
An important step for RFC implementation is for people to experiment with the
80-
implementation and give feedback, especially before stabilization. The following
81-
RFCs would benefit from user testing before moving forward:
79+
implementation and give feedback, especially before stabilization.
8280

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

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

@@ -161,47 +161,33 @@ Revision range: [45acf54e..42245d34](https://perf.rust-lang.org/?start=45acf54ee
161161
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
162162
are the RFCs that were approved for implementation this week:
163163

164-
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
165-
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
166-
<!-- * []() -->
167-
168-
<!--
169-
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
170-
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
171-
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
172-
-->
164+
* *No RFCs were approved this week.*
173165

174166
### Final Comment Period
175167

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

179-
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
180-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
181-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
182-
<!-- * [disposition: ] []() -->
183-
184171
#### Tracking Issues & PRs
185-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
186-
<!-- or if none entered FCP this week, use: -->
187-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
188-
<!-- * [disposition: ] []() -->
189-
190172
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
173+
* [Use lld by default on x86_64-unknown-linux-gnu stable](https://github.com/rust-lang/rust/pull/140525)
174+
* [Allow #[must_use] on associated types to warn on unused values in generic contexts](https://github.com/rust-lang/rust/pull/142590)
175+
* [Fix proc_macro::Ident 's handling of $crate](https://github.com/rust-lang/rust/pull/141996)
176+
* [Ensure non-empty buffers for large vectored I/O](https://github.com/rust-lang/rust/pull/138879)
191177

192-
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
193-
194-
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
178+
##### [Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
179+
* [RFC: --crate-attr](https://github.com/rust-lang/rfcs/pull/3791)
195180

196-
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
181+
*No Items entered Final Comment Period this week for
182+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
183+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
184+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+) or
185+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
197186

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

200189
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
201-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
202-
<!-- or if there are no new or updated RFCs this week, use: -->
203-
<!-- * *No New or Updated RFCs were created this week.* -->
204-
<!-- * [new|updated] []() -->
190+
* *No New or Updated RFCs were created this week.*
205191

206192
## Upcoming Events
207193

0 commit comments

Comments
 (0)