Skip to content

Commit f366c4e

Browse files
Merge pull request #7369 from U007D/main
Update CFT, FCP, MCP and RFC sections for TWiR-629
2 parents 19d0ae2 + 9c317cc commit f366c4e

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
@@ -85,46 +85,14 @@ 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

118-
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
119-
120-
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
121-
122-
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
123-
124-
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
125-
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
126-
need testing.
127-
12896
## Call for Participation; projects and speakers
12997

13098
### CFP - Projects
@@ -178,59 +146,42 @@ Revision range: [eca9d93f..55495234](https://perf.rust-lang.org/?start=eca9d93f9
178146

179147
[Full report here](https://github.com/rust-lang/rustc-perf/blob/1e31d44e9db6e283552733052331af16e14e58e2/triage/2025/2025-12-08.md)
180148

149+
181150
### [Approved RFCs](https://github.com/rust-lang/rfcs/commits/master)
182151

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

186-
<!-- Use either
187-
* [Item title](Item URL)
188-
- or
189-
* *No RFCs were approved this week.*
190-
-->
155+
* *No RFCs entered Final Comment Period this week.*
191156

192157
### Final Comment Period
193158

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

197162
#### Tracking Issues & PRs
198-
<!-- Either remove the group from the "No Items Entered Final Comment Period this week for" section
199-
and add the item(s) which entered Final comment period:
200-
##### [Group](Group URL)
201-
* [Item title](Item URL)
202-
- for `disposition-merge` `final-comment-period` items, or
203-
* [disposition: postpone]
204-
- for `disposition-postpone` `final-comment-period` items, or
205-
* [disposition: close]
206-
- for `disposition-close` `final-comment-period` items,
207-
* [disposition: unspecified]
208-
- when `disposition` is unspecified or ensure the group is a part of the
209-
"No Items Entered Final Comment Period this week for" section
163+
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
164+
* [Warn on codegen attributes on required trait methods](https://github.com/rust-lang/rust/pull/148756)
165+
* [NFC normalize lifetime identifiers](https://github.com/rust-lang/rust/pull/149192)
166+
* [don't normalize where-clauses when checking well-formedness](https://github.com/rust-lang/rust/pull/148477)
167+
168+
[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)
169+
* [Destabilise target-spec-json](https://github.com/rust-lang/compiler-team/issues/944)
170+
171+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
172+
* [RFC: `#[export_visibility = ...]` attribute](https://github.com/rust-lang/rfcs/pull/3834)
173+
210174
*No Items entered Final Comment Period this week for
211-
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
212-
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
213-
[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),
214-
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
215-
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
216-
[Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period) or
217-
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
175+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
176+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
177+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
178+
[Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period) or
179+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
218180

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

222183
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
223-
<!-- Use either
224-
* [Item title](Item URL)
225-
- for new items, or
226-
* [updated] [Item title](Item URL)
227-
- for updated items, or
228184
* *No New or Updated RFCs were created this week.*
229-
-->
230-
231-
<!-- Sample commit message
232-
Update CFT, FCP, MCP and RFC sections for TWiR-xxx
233-
-->
234185

235186
## Upcoming Events
236187

0 commit comments

Comments
 (0)