Skip to content

Commit ad40a35

Browse files
authored
Update RFC, MCP, FCP and CFT sections for TWiR-627 (#7317)
1 parent e278514 commit ad40a35

File tree

1 file changed

+26
-50
lines changed

1 file changed

+26
-50
lines changed

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

Lines changed: 26 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -62,40 +62,19 @@ and just ask the editors to select the category.
6262
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
6363

6464
## Calls for Testing
65+
6566
An important step for RFC implementation is for people to experiment with the
6667
implementation and give feedback, especially before stabilization.
6768

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

72-
<!-- If there are new CfT items this week, include:
73-
74-
[Repo Name](Repo URL)
75-
* [<Feature name>](<Feature URL>)
76-
* [Testing steps](<Testing Steps URL>)
77-
78-
- and make note in the item so the authors know to remove the `call-for-testing` label:
79-
This RFC will appear in the **Call for Testing** section of the next issue (#) of This Week in Rust (TWiR).
80-
You may remove the `call-for-testing` label. Please feel free to leave the `call-for-testing` label in place if you would like this RFC to appear again in another issue of TWiR.
81-
82-
- where `Repo Name` and `Repo URL` are one of:
83-
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
84-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
85-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
86-
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
87-
88-
- and `Testing steps` points directly to the procedures the item wants users to exercise.
89-
90-
- For all `Repo Names` with no new CfT items this week: use (removing the repos for which new
91-
CfT items did appear, of course)
92-
9373
* *No calls for testing were issued this week by
9474
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
95-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
96-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
75+
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing),
76+
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) or
9777
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
98-
-->
9978

10079
[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.
10180

@@ -172,48 +151,45 @@ are the RFCs that were approved for implementation this week:
172151
* *No RFCs were approved this week.*
173152
-->
174153

154+
### [Approved RFCs](https://github.com/rust-lang/rfcs/commits/master)
155+
156+
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
157+
are the RFCs that were approved for implementation this week:
158+
159+
* *No RFCs were approved this week.*
160+
175161
### Final Comment Period
176162

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

180166
#### Tracking Issues & PRs
181-
<!-- Either remove the group from the "No Items Entered Final Comment Period this week for" section
182-
and add the item(s) which entered Final comment period:
183-
##### [Group](Group URL)
184-
* [Item title](Item URL)
185-
- for `disposition-merge` `final-comment-period` items, or
186-
* [disposition: postpone]
187-
- for `disposition-postpone` `final-comment-period` items, or
188-
* [disposition: close]
189-
- for `disposition-close` `final-comment-period` items,
190-
* [disposition: unspecified]
191-
- when `disposition` is unspecified or ensure the group is a part of the
192-
"No Items Entered Final Comment Period this week for" section
167+
168+
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
169+
170+
* [Make closure capturing have consistent and correct behaviour around patterns](https://github.com/rust-lang/rust/pull/138961)
171+
* [misc coercion cleanups and handle safety correctly](https://github.com/rust-lang/rust/pull/148602)
172+
* [Implement `TryFrom<char>` for `usize`.](https://github.com/rust-lang/rust/pull/146792)
173+
* [Contracts: primitive ownership assertions: `owned` and `block`](https://github.com/rust-lang/compiler-team/issues/942)
174+
* [const validation: remove check for mutable refs in final value of const](https://github.com/rust-lang/rust/pull/148746)
175+
193176
*No Items entered Final Comment Period this week for
194-
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
195-
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
196177
[Compiler Team](https://github.com/rust-lang/compiler-team/issues?q=label%3Amajor-change%20%20label%3Afinal-comment-period) [(MCPs only)](https://forge.rust-lang.org/compiler/mcp.html),
178+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
179+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
197180
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
198181
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
199-
[Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period) or
182+
[Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period) or
200183
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
201184

202185
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
203-
-->
204186

205187
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
206-
<!-- Use either
207-
* [Item title](Item URL)
208-
- for new items, or
209-
* [updated] [Item title](Item URL)
210-
- for updated items, or
211-
* *No New or Updated RFCs were created this week.*
212-
-->
213188

214-
<!-- Sample commit message
215-
Update CFT, FCP, MCP and RFC sections for TWiR-xxx
216-
-->
189+
* [RFC: Exhaustive traits. Traits that enable cross trait casting between trait objects.](https://github.com/rust-lang/rfcs/pull/3885)
190+
* [CMSE calling conventions](https://github.com/rust-lang/rfcs/pull/3884)
191+
* [`RUSTC_ALLOW_UNSTABLE_<feature>`: a `RUSTC_BOOTSTRAP` alternative](https://github.com/rust-lang/rfcs/pull/3882)
192+
* [Target Stages, an improvement of the incremental system](https://github.com/rust-lang/rfcs/pull/3881)
217193

218194
## Upcoming Events
219195

0 commit comments

Comments
 (0)