Skip to content

Commit ba10e22

Browse files
Merge pull request #7398 from tzilist/main
Update CFT, FCP, MCP and RFC sections for TWiR-630
2 parents 78ecad7 + 1bd87a5 commit ba10e22

File tree

1 file changed

+19
-67
lines changed

1 file changed

+19
-67
lines changed

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

Lines changed: 19 additions & 67 deletions
Original file line numberDiff line numberDiff line change
@@ -84,45 +84,14 @@ If you are a feature implementer and would like your RFC to appear in this list,
8484
`call-for-testing` label to your RFC along with a comment providing testing instructions and/or
8585
guidance on which aspect(s) of the feature need testing.
8686

87-
<!-- If there are new CfT items this week, include:
88-
89-
[Repo Name](Repo URL)
90-
* [<Feature name>](<Feature URL>)
91-
* [Testing steps](<Testing Steps URL>)
92-
93-
- and make note in the item so the authors know to remove the `call-for-testing` label:
94-
This RFC will appear in the **Call for Testing** section of the next issue (#) of This Week in Rust (TWiR).
95-
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.
96-
97-
- where `Repo Name` and `Repo URL` are one of:
98-
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
99-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
100-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
101-
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
102-
103-
- and `Testing steps` points directly to the procedures the item wants users to exercise.
104-
105-
- For all `Repo Names` with no new CfT items this week: use (removing the repos for which new
106-
CfT items did appear, of course)
107-
10887
* *No calls for testing were issued this week by
10988
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
110-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
111-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
89+
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing),
90+
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) or
11291
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
113-
-->
11492

11593
[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.
11694

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

12796
## Call for Participation; projects and speakers
12897

@@ -163,55 +132,38 @@ If you are an event organizer hoping to expand the reach of your event, please s
163132

164133
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
165134
are the RFCs that were approved for implementation this week:
166-
167-
<!-- Use either
168-
* [Item title](Item URL)
169-
- or
170-
* *No RFCs were approved this week.*
171-
-->
135+
* [Adding a crates.io Security tab](https://github.com/rust-lang/rfcs/pull/3872)
172136

173137
### Final Comment Period
174138

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

178142
#### Tracking Issues & PRs
179-
<!-- Either remove the group from the "No Items Entered Final Comment Period this week for" section
180-
and add the item(s) which entered Final comment period:
181-
##### [Group](Group URL)
182-
* [Item title](Item URL)
183-
- for `disposition-merge` `final-comment-period` items, or
184-
* [disposition: postpone]
185-
- for `disposition-postpone` `final-comment-period` items, or
186-
* [disposition: close]
187-
- for `disposition-close` `final-comment-period` items,
188-
* [disposition: unspecified]
189-
- when `disposition` is unspecified or ensure the group is a part of the
190-
"No Items Entered Final Comment Period this week for" section
143+
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
144+
* [Don't strip shebang in expr-ctxt `include!(…)`](https://github.com/rust-lang/rust/pull/146377)
145+
* [Policy on the use of `rustc_legacy_const_generics` in stdarch](https://github.com/rust-lang/rust/issues/149654)
146+
* [Tracking Issue for `atomic_try_update`](https://github.com/rust-lang/rust/issues/135894)
147+
148+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
149+
* [build-std: context](https://github.com/rust-lang/rfcs/pull/3873)
150+
151+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
152+
* [feat(index): Stabilize pubtime](https://github.com/rust-lang/cargo/pull/16372)
153+
154+
[Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period)
155+
* [Add alumni policy](https://github.com/rust-lang/leadership-council/pull/218)
156+
191157
*No Items entered Final Comment Period this week for
192-
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
193-
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
194158
[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),
195159
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
196-
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
197-
[Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period) or
160+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc) or
198161
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
199162

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

203165
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
204-
<!-- Use either
205-
* [Item title](Item URL)
206-
- for new items, or
207-
* [updated] [Item title](Item URL)
208-
- for updated items, or
209-
* *No New or Updated RFCs were created this week.*
210-
-->
211-
212-
<!-- Sample commit message
213-
Update CFT, FCP, MCP and RFC sections for TWiR-xxx
214-
-->
166+
* [RFC: Open up your enum with an unnamed variant](https://github.com/rust-lang/rfcs/pull/3894)
215167

216168
## Upcoming Events
217169

0 commit comments

Comments
 (0)