Skip to content

Commit 2685fad

Browse files
committed
Update RFC, MCP, FCP and CFT sections for TWiR-618
1 parent 5140456 commit 2685fad

File tree

1 file changed

+14
-63
lines changed

1 file changed

+14
-63
lines changed

draft/2025-09-24-this-week-in-rust.md

Lines changed: 14 additions & 63 deletions
Original file line numberDiff line numberDiff line change
@@ -62,52 +62,20 @@ 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-
An important step for feature implementation is for people to experiment with the
65+
An important step for RFC implementation is for people to experiment with the
6666
implementation and give feedback, especially before stabilization.
6767

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

72-
<!-- If there are new CfT items this week, use: -->
73-
<!--
74-
[Repo Name](Repo URL)
75-
* [<Feature name>](<Feature URL>)
76-
* [Testing steps](<Testing Steps URL>)
77-
-->
78-
<!-- where `Repo Name` and `Repo URL` are one of:
79-
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
80-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
81-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
82-
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
83-
-->
84-
85-
<!-- For all `Repo Names` with no new CfT items this week: use (removing the repos for which new
86-
CfT items did appear, of course) -->
87-
<!--
8872
* *No calls for testing were issued this week by
8973
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
9074
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
9175
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
9276
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
93-
-->
94-
* *No calls for testing were issued this week by [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
97-
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
9877

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

11280
## Call for Participation; projects and speakers
11381

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

151-
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
152-
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
153-
<!-- * []() -->
154-
155-
<!--
156-
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
157-
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
158-
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
159-
-->
119+
* *No RFCs were approved this week.*
160120

161121
### Final Comment Period
162122

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

166-
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
167-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
168-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
169-
<!-- * [disposition: ] []() -->
170-
171126
#### Tracking Issues & PRs
172-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
173-
<!-- or if none entered FCP this week, use: -->
174-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
175-
<!-- * [disposition: ] []() -->
176-
177127
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
128+
* [the `#[track_caller]` shim should not inherit `#[no_mangle]`](https://github.com/rust-lang/rust/pull/145724)
129+
* [Allow borrowing array elements from packed structs with ABI align <= packed align](https://github.com/rust-lang/rust/pull/145419)
178130

179-
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
180-
181-
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
182-
183-
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
131+
*No Items entered Final Comment Period this week for
132+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
133+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
134+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
135+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
136+
[Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period) or
137+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
184138

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

187141
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
188-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
189-
<!-- or if there are no new or updated RFCs this week, use: -->
190-
<!-- * *No New or Updated RFCs were created this week.* -->
191-
<!-- * [new|updated] []() -->
142+
* [RFC: Add iter! macro](https://github.com/rust-lang/rfcs/pull/3861)
192143

193144
## Upcoming Events
194145

0 commit comments

Comments
 (0)