Skip to content

Commit e86456b

Browse files
Merge pull request #7235 from tzilist/master
Add notice in Calls for Testing and add missing section in Final Comment Period for TWiR-624
2 parents f517b72 + 64b18bf commit e86456b

File tree

1 file changed

+6
-24
lines changed

1 file changed

+6
-24
lines changed

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

Lines changed: 6 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -85,33 +85,11 @@ If you are a feature implementer and would like your RFC to appear in this list,
8585
`call-for-testing` label to your RFC along with a comment providing testing instructions and/or
8686
guidance on which aspect(s) of the feature need testing.
8787

88-
<!-- If there are new CfT items this week, include:
89-
90-
[Repo Name](Repo URL)
91-
* [<Feature name>](<Feature URL>)
92-
* [Testing steps](<Testing Steps URL>)
93-
94-
- and make note in the item so the authors know to remove the `call-for-testing` label:
95-
This RFC will appear in the **Call for Testing** section of the next issue (#) of This Week in Rust (TWiR).
96-
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.
97-
98-
- where `Repo Name` and `Repo URL` are one of:
99-
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
100-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
101-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
102-
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
103-
104-
- and `Testing steps` points directly to the procedures the item wants users to exercise.
105-
106-
- For all `Repo Names` with no new CfT items this week: use (removing the repos for which new
107-
CfT items did appear, of course)
108-
10988
* *No calls for testing were issued this week by
11089
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
111-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
112-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
90+
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing),
91+
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) or
11392
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
114-
-->
11593

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

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

256+
##### [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)
257+
258+
* [remove support for `typeof`](https://github.com/rust-lang/compiler-team/issues/940)
259+
278260
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
279261

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

0 commit comments

Comments
 (0)