Skip to content

Add notice in Calls for Testing and add missing section in Final Comment Period for TWiR-624 #7235

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 6, 2025
Merged

Add notice in Calls for Testing and add missing section in Final Comment Period for TWiR-624 #7235

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5b31dde
Update CFT, FCP, MCP and RFC sections for TWiR-624, fix FCP and Calls…
tzilist Nov 5, 2025
64b18bf
merge master
tzilist Nov 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 6 additions & 24 deletions draft/2025-11-05-this-week-in-rust.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,33 +85,11 @@ If you are a feature implementer and would like your RFC to appear in this list,
`call-for-testing` label to your RFC along with a comment providing testing instructions and/or
guidance on which aspect(s) of the feature need testing.

<!-- If there are new CfT items this week, include:

[Repo Name](Repo URL)
* [<Feature name>](<Feature URL>)
* [Testing steps](<Testing Steps URL>)

- and make note in the item so the authors know to remove the `call-for-testing` label:
This RFC will appear in the **Call for Testing** section of the next issue (#) of This Week in Rust (TWiR).
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.

- where `Repo Name` and `Repo URL` are one of:
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)

- and `Testing steps` points directly to the procedures the item wants users to exercise.

- For all `Repo Names` with no new CfT items this week: use (removing the repos for which new
CfT items did appear, of course)

* *No calls for testing were issued this week by
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing),
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) or
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
-->

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

Expand Down Expand Up @@ -275,6 +253,10 @@ which are reaching a decision. Express your opinions now.
* [Make deref_nullptr deny by default instead of warn](https://github.com/rust-lang/rust/pull/148122)
* [Tracking Issue for `const_mul_add`](https://github.com/rust-lang/rust/issues/146724)

##### [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)

* [remove support for `typeof`](https://github.com/rust-lang/compiler-team/issues/940)

##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)

* [Guarantee the binary representation of `isize` explicitly](https://github.com/rust-lang/reference/pull/2064)
Expand Down