Skip to content

Commit 0262e06

Browse files
U007DU007D
committed
Update RFC, MCP, FCP and CFT sections for TWiR-607
1 parent fbac60b commit 0262e06

File tree

1 file changed

+14
-63
lines changed

1 file changed

+14
-63
lines changed

‎draft/2025-07-09-this-week-in-rust.md‎

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

5959
## Calls for Testing
60-
An important step for feature implementation is for people to experiment with the
60+
An important step for RFC implementation is for people to experiment with the
6161
implementation and give feedback, especially before stabilization.
6262

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

67-
<!-- If there are new CfT items this week, use: -->
68-
<!--
69-
[Repo Name](Repo URL)
70-
* [<Feature name>](<Feature URL>)
71-
* [Testing steps](<Testing Steps URL>)
72-
-->
73-
<!-- where `Repo Name` and `Repo URL` are one of:
74-
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
75-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
76-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
77-
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
78-
-->
79-
80-
<!-- For all `Repo Names` with no new CfT items this week: use (removing the repos for which new
81-
CfT items did appear, of course) -->
82-
<!--
83-
* *No calls for testing were issued this week by
84-
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
85-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
86-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
87-
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
88-
-->
8967
* *No calls for testing were issued this week by [Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
9068
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
9169
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
9270
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
9371

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

10774
## Call for Participation; projects and speakers
10875

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

146-
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
147-
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
148-
<!-- * []() -->
149-
150-
<!--
151-
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
152-
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
153-
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
154-
-->
113+
* [Declarative `macro_rules!` derive macros](https://github.com/rust-lang/rfcs/pull/3698)
114+
* [Declarative `macro_rules!` attribute macros](https://github.com/rust-lang/rfcs/pull/3697)
155115

156116
### Final Comment Period
157117

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

161-
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
162-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
163-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
164-
<!-- * [disposition: ] []() -->
165-
166121
#### Tracking Issues & PRs
167-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
168-
<!-- or if none entered FCP this week, use: -->
169-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
170-
<!-- * [disposition: ] []() -->
171-
172122
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
173-
174-
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
175-
176-
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
123+
* [Tracking Issue for `const_slice_reverse`](https://github.com/rust-lang/rust/issues/135120)
177124

178125
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
126+
* [&str and &[u8] have the same layout](https://github.com/rust-lang/reference/pull/1848)
127+
128+
*No Items entered Final Comment Period this week for
129+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
130+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
131+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+) or
132+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
179133

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

182136
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
183-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
184-
<!-- or if there are no new or updated RFCs this week, use: -->
185-
<!-- * *No New or Updated RFCs were created this week.* -->
186-
<!-- * [new|updated] []() -->
137+
* *No New or Updated RFCs were created this week.*
187138

188139
## Upcoming Events
189140

0 commit comments

Comments
 (0)