Skip to content

Commit c4d2efc

Browse files
Merge pull request #6632 from U007D/master
Update RFC, MCP, FCP and CFT sections for TWiR-599
2 parents 3bae06b + a5d6103 commit c4d2efc

File tree

1 file changed

+33
-42
lines changed

1 file changed

+33
-42
lines changed

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

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

7171
## Calls for Testing
72-
7372
An important step for RFC implementation is for people to experiment with the
74-
implementation and give feedback, especially before stabilization. The following
75-
RFCs would benefit from user testing before moving forward:
73+
implementation and give feedback, especially before stabilization.
7674

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

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

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

135-
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
136-
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
137-
<!-- * []() -->
138-
139-
<!--
140-
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
141-
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
142-
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
143-
-->
134+
* *No RFCs were approved this week.*
144135

145136
### Final Comment Period
146137

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

150-
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
151-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
152-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
153-
<!-- * [disposition: ] []() -->
154-
155141
#### Tracking Issues & PRs
156-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
157-
<!-- or if none entered FCP this week, use: -->
158-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
159-
<!-- * [disposition: ] []() -->
160-
161142
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
162-
163-
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
164-
165-
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
166-
167-
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
168-
169-
##### [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
143+
* [Tracking Issue for `non_null_from_ref`](https://github.com/rust-lang/rust/issues/130823)
144+
* [Add std::io::Seek instance for `std::io::Take`](https://github.com/rust-lang/rust/pull/138023)
145+
* [aarch64-softfloat: forbid enabling the neon target feature](https://github.com/rust-lang/rust/pull/135160)
146+
* [Stabilize the avx512 target features](https://github.com/rust-lang/rust/pull/138940)
147+
* [make std::intrinsics functions actually be intrinsics](https://github.com/rust-lang/rust/pull/139916)
148+
* [Error on recursive opaque ty in HIR typeck](https://github.com/rust-lang/rust/pull/139419)
149+
* [Remove `i128` and `u128` from `improper_ctypes_definitions`](https://github.com/rust-lang/rust/pull/137306)
150+
* [Guarantee behavior of transmuting `Option::<T>::None` subject to NPO](https://github.com/rust-lang/rust/pull/137323)
151+
* [Temporary lifetime extension through tuple struct and tuple variant constructors](https://github.com/rust-lang/rust/pull/140593)
152+
* [Stabilize `tcp_quickack`](https://github.com/rust-lang/rust/pull/129121)
153+
* [Change the desugaring of `assert!` for better error output](https://github.com/rust-lang/rust/pull/122661)
154+
* [Make well-formedness predicates no longer coinductive](https://github.com/rust-lang/rust/pull/140208)
155+
156+
*No Items entered Final Comment Period this week for
157+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
158+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
159+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
160+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+) or
161+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
162+
163+
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
170164

171165
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
172-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
173-
<!-- or if there are no new or updated RFCs this week, use: -->
174-
<!-- * *No New or Updated RFCs were created this week.* -->
175-
<!-- * [new|updated] []() -->
166+
* [RFC: Extended Standard Library (ESL)](https://github.com/rust-lang/rfcs/pull/3810)
176167

177168
## Upcoming Events
178169

0 commit comments

Comments
 (0)