Skip to content

Commit 5b31dde

Browse files
committed
Update CFT, FCP, MCP and RFC sections for TWiR-624, fix FCP and Calls for Testing
1 parent ec52139 commit 5b31dde

File tree

1 file changed

+32
-56
lines changed

1 file changed

+32
-56
lines changed

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

Lines changed: 32 additions & 56 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

@@ -148,54 +127,51 @@ If you are an event organizer hoping to expand the reach of your event, please s
148127
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
149128
are the RFCs that were approved for implementation this week:
150129

151-
<!-- Use either
152-
* [Item title](Item URL)
153-
- or
154130
* *No RFCs were approved this week.*
155-
-->
156131

157132
### Final Comment Period
158133

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

162137
#### Tracking Issues & PRs
163-
<!-- Either remove the group from the "No Items Entered Final Comment Period this week for" section
164-
and add the item(s) which entered Final comment period:
165-
##### [Group](Group URL)
166-
* [Item title](Item URL)
167-
- for `disposition-merge` `final-comment-period` items, or
168-
* [disposition: postpone]
169-
- for `disposition-postpone` `final-comment-period` items, or
170-
* [disposition: close]
171-
- for `disposition-close` `final-comment-period` items,
172-
* [disposition: unspecified]
173-
- when `disposition` is unspecified or ensure the group is a part of the
174-
"No Items Entered Final Comment Period this week for" section
138+
139+
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
140+
141+
* [Emit error when using path-segment keyword as cfg pred](https://github.com/rust-lang/rust/pull/146978)
142+
* [stabilize extern_system_varargs](https://github.com/rust-lang/rust/pull/145954)
143+
* [Tracking issue for `vec_into_raw_parts`](https://github.com/rust-lang/rust/issues/65816)
144+
* [rustdoc: Erase `#![doc(document_private_items)]`](https://github.com/rust-lang/rust/pull/146495)
145+
* [Add new `function_casts_as_integer` lint](https://github.com/rust-lang/rust/pull/141470)
146+
* [resolve: Preserve ambiguous glob reexports in crate metadata](https://github.com/rust-lang/rust/pull/147984)
147+
* [Make deref_nullptr deny by default instead of warn](https://github.com/rust-lang/rust/pull/148122)
148+
* [Tracking Issue for `const_mul_add`](https://github.com/rust-lang/rust/issues/146724)
149+
150+
##### [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)
151+
152+
* [remove support for `typeof`](https://github.com/rust-lang/compiler-team/issues/940)
153+
154+
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
155+
156+
* [Guarantee the binary representation of `isize` explicitly](https://github.com/rust-lang/reference/pull/2064)
157+
158+
##### [Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period)
159+
160+
* [Proposal: Require all project team members to have Zulip IDs](https://github.com/rust-lang/leadership-council/issues/228)
161+
175162
*No Items entered Final Comment Period this week for
176-
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
177163
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
178-
[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),
179-
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
180-
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
181-
[Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period) or
164+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
165+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+) or
182166
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
183167

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

187170
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
188-
<!-- Use either
189-
* [Item title](Item URL)
190-
- for new items, or
191-
* [updated] [Item title](Item URL)
192-
- for updated items, or
193-
* *No New or Updated RFCs were created this week.*
194-
-->
195171

196-
<!-- Sample commit message
197-
Update CFT, FCP, MCP and RFC sections for TWiR-xxx
198-
-->
172+
* [build-std: explicit dependencies](https://github.com/rust-lang/rfcs/pull/3875)
173+
* [build-std: always](https://github.com/rust-lang/rfcs/pull/3874)
174+
* [build-std: context](https://github.com/rust-lang/rfcs/pull/3873)
199175

200176
## Upcoming Events
201177

0 commit comments

Comments
 (0)