Skip to content

Commit c422488

Browse files
Merge pull request #6824 from U007D/master
Update RFC, MCP, FCP and CFT sections for TWiR-608
2 parents 35702ee + 1a977a0 commit c422488

File tree

1 file changed

+17
-62
lines changed

1 file changed

+17
-62
lines changed

draft/2025-07-16-this-week-in-rust.md

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

6666
## Calls for Testing
67-
An important step for feature implementation is for people to experiment with the
67+
An important step for RFC implementation is for people to experiment with the
6868
implementation and give feedback, especially before stabilization.
6969

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

74-
<!-- If there are new CfT items this week, use: -->
75-
<!--
76-
[Repo Name](Repo URL)
77-
* [<Feature name>](<Feature URL>)
78-
* [Testing steps](<Testing Steps URL>)
79-
-->
80-
<!-- where `Repo Name` and `Repo URL` are one of:
81-
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
82-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
83-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
84-
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
85-
-->
86-
87-
<!-- For all `Repo Names` with no new CfT items this week: use (removing the repos for which new
88-
CfT items did appear, of course) -->
89-
<!--
90-
* *No calls for testing were issued this week by
91-
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
92-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
93-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
94-
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
95-
-->
9674
* *No calls for testing were issued this week by [Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
9775
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
9876
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
9977
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
10078

10179
[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.
102-
-->
103-
104-
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
105-
106-
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
107-
108-
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
109-
110-
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
111-
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
112-
need testing.
11380

11481
## Call for Participation; projects and speakers
11582

@@ -171,47 +138,35 @@ Revision range: [0d11be5a..a9fb6103](https://perf.rust-lang.org/?start=0d11be5aa
171138
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
172139
are the RFCs that were approved for implementation this week:
173140

174-
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
175-
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
176-
<!-- * []() -->
177-
178-
<!--
179-
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
180-
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
181-
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
182-
-->
141+
* *No RFCs were approved this week.*
183142

184143
### Final Comment Period
185144

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

189-
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
190-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
191-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
192-
<!-- * [disposition: ] []() -->
193-
194148
#### Tracking Issues & PRs
195-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
196-
<!-- or if none entered FCP this week, use: -->
197-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
198-
<!-- * [disposition: ] []() -->
199-
200149
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
150+
* [Guarantee 8 bytes of alignment in Thread::into_raw](https://github.com/rust-lang/rust/pull/143859)
151+
* [rustdoc: add ways of collapsing all impl blocks](https://github.com/rust-lang/rust/pull/141663)
152+
* [Stabilize `const_float_round_methods`](https://github.com/rust-lang/rust/pull/143604)
153+
* [Tracking Issue for `#![feature(const_float_round_methods)]`](https://github.com/rust-lang/rust/issues/141555)
154+
* [Add `target_env = "macabi"` and `target_env = "sim"`](https://github.com/rust-lang/rust/pull/139451)
201155

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

204-
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
157+
##### [Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
158+
* [Closing issues relevant to T-lang on this repo](https://github.com/rust-lang/rfcs/issues/3756)
205159

206-
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
160+
*No Items entered Final Comment Period this week for
161+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
162+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
163+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc) or
164+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
207165

208-
##### [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
166+
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
209167

210168
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
211-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
212-
<!-- or if there are no new or updated RFCs this week, use: -->
213-
<!-- * *No New or Updated RFCs were created this week.* -->
214-
<!-- * [new|updated] []() -->
169+
* [new] [repr(scalable)](https://github.com/rust-lang/rfcs/pull/3838)
215170

216171
## Upcoming Events
217172

0 commit comments

Comments
 (0)