Skip to content

Commit f5a0077

Browse files
Merge pull request #7024 from U007D/main
Update RFC, MCP, FCP and CFT sections for TWiR-617
2 parents 9497526 + 96b6a0c commit f5a0077

File tree

1 file changed

+21
-65
lines changed

1 file changed

+21
-65
lines changed

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

Lines changed: 21 additions & 65 deletions
Original file line numberDiff line numberDiff line change
@@ -74,52 +74,20 @@ and just ask the editors to select the category.
7474
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
7575

7676
## Calls for Testing
77-
An important step for feature implementation is for people to experiment with the
77+
An important step for RFC implementation is for people to experiment with the
7878
implementation and give feedback, especially before stabilization.
7979

80-
If you are a feature implementer and would like your feature to appear in this list, add a
80+
If you are a feature implementer and would like your RFC to appear in this list, add a
8181
`call-for-testing` label to your RFC along with a comment providing testing instructions and/or
8282
guidance on which aspect(s) of the feature need testing.
8383

84-
<!-- If there are new CfT items this week, use: -->
85-
<!--
86-
[Repo Name](Repo URL)
87-
* [<Feature name>](<Feature URL>)
88-
* [Testing steps](<Testing Steps URL>)
89-
-->
90-
<!-- where `Repo Name` and `Repo URL` are one of:
91-
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
92-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
93-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
94-
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
95-
-->
96-
97-
<!-- For all `Repo Names` with no new CfT items this week: use (removing the repos for which new
98-
CfT items did appear, of course) -->
99-
<!--
10084
* *No calls for testing were issued this week by
10185
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
10286
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
10387
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
10488
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
105-
-->
106-
* *No calls for testing were issued this week by [Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
107-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
108-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
109-
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
11089

11190
[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.
112-
-->
113-
114-
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
115-
116-
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
117-
118-
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
119-
120-
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
121-
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
122-
need testing.
12391

12492
## Call for Participation; projects and speakers
12593

@@ -180,47 +148,35 @@ Revision range: [f13ef0d7..52618eb3](https://perf.rust-lang.org/?start=f13ef0d75
180148
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
181149
are the RFCs that were approved for implementation this week:
182150

183-
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
184-
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
185-
<!-- * []() -->
186-
187-
<!--
188-
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
189-
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
190-
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
191-
-->
151+
* *No RFCs were approved this week.*
192152

193153
### Final Comment Period
194154

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

198-
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
199-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
200-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
201-
<!-- * [disposition: ] []() -->
202-
203158
#### Tracking Issues & PRs
204-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
205-
<!-- or if none entered FCP this week, use: -->
206-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
207-
<!-- * [disposition: ] []() -->
208-
209159
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
210-
211-
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
212-
213-
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
214-
215-
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
216-
217-
##### [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
160+
* [Allow &raw `[mut | const]` for union field in safe code](https://github.com/rust-lang/rust/pull/141469)
161+
* [Deny-by-default never type lints](https://github.com/rust-lang/rust/pull/146167)
162+
* [Opportunistically split `!=` to successfully parse never type](https://github.com/rust-lang/rust/pull/145536)
163+
* [Allow specifying multiple bounds for same associated item, except in trait objects](https://github.com/rust-lang/rust/pull/146593)
164+
* [rustdoc: hide `#[repr]` if it isn't part of the public ABI](https://github.com/rust-lang/rust/pull/116882)
165+
166+
*No Items entered Final Comment Period this week for
167+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
168+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
169+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
170+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
171+
[Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period) or
172+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
173+
174+
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
218175

219176
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
220-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
221-
<!-- or if there are no new or updated RFCs this week, use: -->
222-
<!-- * *No New or Updated RFCs were created this week.* -->
223-
<!-- * [new|updated] []() -->
177+
* [RFC: `#[cfg(since(rust, "1.95"))]` for Rust-version conditional compilation](https://github.com/rust-lang/rfcs/pull/3857)
178+
* [Mitigation enforcement](https://github.com/rust-lang/rfcs/pull/3855)
179+
* [RFC for `#[stable(since)]`](https://github.com/rust-lang/rfcs/pull/3854)
224180

225181
## Upcoming Events
226182

0 commit comments

Comments
 (0)