Skip to content

Commit 9c317cc

Browse files
committed
Update CFT, FCP, MCP and RFC sections for TWiR-629
1 parent 404f088 commit 9c317cc

File tree

1 file changed

+20
-69
lines changed

1 file changed

+20
-69
lines changed

draft/2025-12-10-this-week-in-rust.md

Lines changed: 20 additions & 69 deletions
Original file line numberDiff line numberDiff line change
@@ -69,46 +69,14 @@ If you are a feature implementer and would like your RFC to appear in this list,
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, include:
73-
74-
[Repo Name](Repo URL)
75-
* [<Feature name>](<Feature URL>)
76-
* [Testing steps](<Testing Steps URL>)
77-
78-
- and make note in the item so the authors know to remove the `call-for-testing` label:
79-
This RFC will appear in the **Call for Testing** section of the next issue (#) of This Week in Rust (TWiR).
80-
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.
81-
82-
- where `Repo Name` and `Repo URL` are one of:
83-
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
84-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
85-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
86-
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
87-
88-
- and `Testing steps` points directly to the procedures the item wants users to exercise.
89-
90-
- For all `Repo Names` with no new CfT items this week: use (removing the repos for which new
91-
CfT items did appear, of course)
92-
9372
* *No calls for testing were issued this week by
9473
[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
74+
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing),
75+
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) or
9776
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
98-
-->
9977

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

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.
111-
11280
## Call for Participation; projects and speakers
11381

11482
### CFP - Projects
@@ -143,59 +111,42 @@ If you are an event organizer hoping to expand the reach of your event, please s
143111

144112
<!-- Perf results go here -->
145113

114+
146115
### [Approved RFCs](https://github.com/rust-lang/rfcs/commits/master)
147116

148117
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
149118
are the RFCs that were approved for implementation this week:
150119

151-
<!-- Use either
152-
* [Item title](Item URL)
153-
- or
154-
* *No RFCs were approved this week.*
155-
-->
120+
* *No RFCs entered Final Comment Period this week.*
156121

157122
### Final Comment Period
158123

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

162127
#### Tracking Issues & PRs
163-
<!-- Either remove the group from the "No Items Entered Final Comment Period this week for" section
164-
and add the item(s) which entered Final comment period:
165-
##### [Group](Group URL)
166-
* [Item title](Item URL)
167-
- for `disposition-merge` `final-comment-period` items, or
168-
* [disposition: postpone]
169-
- for `disposition-postpone` `final-comment-period` items, or
170-
* [disposition: close]
171-
- for `disposition-close` `final-comment-period` items,
172-
* [disposition: unspecified]
173-
- when `disposition` is unspecified or ensure the group is a part of the
174-
"No Items Entered Final Comment Period this week for" section
128+
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
129+
* [Warn on codegen attributes on required trait methods](https://github.com/rust-lang/rust/pull/148756)
130+
* [NFC normalize lifetime identifiers](https://github.com/rust-lang/rust/pull/149192)
131+
* [don't normalize where-clauses when checking well-formedness](https://github.com/rust-lang/rust/pull/148477)
132+
133+
[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)
134+
* [Destabilise target-spec-json](https://github.com/rust-lang/compiler-team/issues/944)
135+
136+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
137+
* [RFC: `#[export_visibility = ...]` attribute](https://github.com/rust-lang/rfcs/pull/3834)
138+
175139
*No Items entered Final Comment Period this week for
176-
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
177-
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
178-
[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),
179-
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
180-
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
181-
[Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period) or
182-
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
140+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
141+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
142+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
143+
[Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period) or
144+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
183145

184146
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
185-
-->
186147

187148
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
188-
<!-- Use either
189-
* [Item title](Item URL)
190-
- for new items, or
191-
* [updated] [Item title](Item URL)
192-
- for updated items, or
193149
* *No New or Updated RFCs were created this week.*
194-
-->
195-
196-
<!-- Sample commit message
197-
Update CFT, FCP, MCP and RFC sections for TWiR-xxx
198-
-->
199150

200151
## Upcoming Events
201152

0 commit comments

Comments
 (0)