Skip to content

Commit f0373f9

Browse files
authored
Merge pull request #6243 from U007D/master
Update RFC, MCP, FCP and CFT sections for TWiR-580
2 parents 0d944a0 + 1448fa8 commit f0373f9

File tree

1 file changed

+13
-31
lines changed

1 file changed

+13
-31
lines changed

draft/2025-01-01-this-week-in-rust.md

Lines changed: 13 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -54,25 +54,18 @@ and just ask the editors to select the category.
5454
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
5555

5656
## Calls for Testing
57-
5857
An important step for RFC implementation is for people to experiment with the
5958
implementation and give feedback, especially before stabilization. The following
6059
RFCs would benefit from user testing before moving forward:
6160

62-
<!-- Calls for Testing go here, use this format:
63-
* [<RFC Topic>](<RFC URL>)
64-
* [Tracking Issue](<Tracking Issue URL>)
65-
* [Testing steps](<Testing Steps URL>)
66-
-->
67-
<!-- or if there are no new or updated RFCs this week, use: -->
68-
<!-- * *No New or Updated RFCs were created this week.* -->
69-
<!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
70-
7161
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
62+
* *No calls for testing were issued this week.*
7263

7364
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
65+
* *No calls for testing were issued this week.*
7466

7567
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
68+
* *No calls for testing were issued this week.*
7669

7770
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
7871
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
@@ -126,47 +119,36 @@ Revision range: [0eca4dd3..93722f7e](https://perf.rust-lang.org/?start=0eca4dd32
126119
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
127120
are the RFCs that were approved for implementation this week:
128121

129-
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
130-
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
131-
<!-- * []() -->
132-
133-
<!--
134-
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
135-
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
136-
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
137-
-->
122+
* *No RFCs were approved this week.*
138123

139124
### Final Comment Period
140125

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

144129
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
145-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
146-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
147-
<!-- * [disposition: ] []() -->
130+
* *No RFCs entered Final Comment Period this week.*
148131

149132
#### Tracking Issues & PRs
150-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
151-
<!-- or if none entered FCP this week, use: -->
152-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
153-
<!-- * [disposition: ] []() -->
154-
155133
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
134+
* *No RFCs entered Final Comment Period this week.*
156135

157136
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
137+
* *No Cargo Tracking Issues or PRs entered Final Comment Period this week.*
158138

159139
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
140+
* *No Language Team Proposals entered Final Comment Period this week.*
160141

161142
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
143+
* *No Language Reference RFCs entered Final Comment Period this week.*
162144

163145
##### [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
146+
* *No Unsafe Code Guideline Tracking Issues or PRs entered Final Comment Period this week.*
164147

165148
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
166-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
167-
<!-- or if there are no new or updated RFCs this week, use: -->
168-
<!-- * *No New or Updated RFCs were created this week.* -->
169-
<!-- * [new|updated] []() -->
149+
* [new] [RFC: `Foo { .. }` pattern matches non-struct types](https://github.com/rust-lang/rfcs/pull/3753)
150+
* [new] [RFC: add LLM text version to rustdoc](https://github.com/rust-lang/rfcs/pull/3751)
151+
* [new] [RFC: cfg_os_version_min](https://github.com/rust-lang/rfcs/pull/3750)
170152

171153
## Upcoming Events
172154

0 commit comments

Comments
 (0)