Skip to content

Commit af03d2a

Browse files
authored
Merge pull request #6656 from U007D/master
Update RFC, MCP, FCP and CFT sections for TWiR-600
2 parents 6d4602f + 4b77766 commit af03d2a

File tree

1 file changed

+18
-49
lines changed

1 file changed

+18
-49
lines changed

draft/2025-05-21-this-week-in-rust.md

Lines changed: 18 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -61,29 +61,16 @@ 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)
67+
If you are a feature implementer and would like your RFC to appear in this list, add a
68+
`call-for-testing` label to your RFC along with a comment providing testing instructions and/or
69+
guidance on which aspect(s) of the feature need testing.
7970

80-
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
81-
82-
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
83-
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.
71+
* *No calls for testing were issued this week by [Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
72+
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) or
73+
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
8774

8875
## Call for Participation; projects and speakers
8976

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

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

137116
### Final Comment Period
138117

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

142-
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
143-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
144-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
145-
<!-- * [disposition: ] []() -->
146-
147121
#### Tracking Issues & PRs
148-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
149-
<!-- or if none entered FCP this week, use: -->
150-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
151-
<!-- * [disposition: ] []() -->
152-
153122
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
123+
* [Tracking Issue for AVX512 intrinsics](https://github.com/rust-lang/rust/issues/111137)
124+
* [rustdoc: on mobile, make the sidebar full width and linewrap](https://github.com/rust-lang/rust/pull/139831)
154125

155-
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
156-
157-
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
158-
159-
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
126+
*No Items entered Final Comment Period this week for
127+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
128+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
129+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
130+
[Language Team](https://github.com/rust-lang/lang-team/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).*
160132

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

163135
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
164-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
165-
<!-- or if there are no new or updated RFCs this week, use: -->
166-
<!-- * *No New or Updated RFCs were created this week.* -->
167-
<!-- * [new|updated] []() -->
136+
* *No New or Updated RFCs were created this week.*
168137

169138
## Upcoming Events
170139

0 commit comments

Comments
 (0)