Skip to content

Commit 753c471

Browse files
authored
Merge pull request #6188 from U007D/master
Update RFC, MCP, FCP and CFT sections for TWiR-577
2 parents 9b028b8 + 474c825 commit 753c471

File tree

1 file changed

+22
-30
lines changed

1 file changed

+22
-30
lines changed

draft/2024-12-11-this-week-in-rust.md

Lines changed: 22 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -74,19 +74,22 @@ Thanks to [Aleksey Sidorov](https://users.rust-lang.org/t/crate-of-the-week/2704
7474
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
7575

7676
## Calls for Testing
77-
7877
An important step for RFC implementation is for people to experiment with the
7978
implementation and give feedback, especially before stabilization. The following
8079
RFCs would benefit from user testing before moving forward:
8180

82-
<!-- Calls for Testing go here, use this format:
83-
* [<RFC Topic>](<RFC URL>)
84-
* [Tracking Issue](<Tracking Issue URL>)
85-
* [Testing steps](<Testing Steps URL>)
86-
-->
87-
<!-- or if there are no new or updated RFCs this week, use: -->
88-
<!-- * *No New or Updated RFCs were created this week.* -->
89-
<!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
81+
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
82+
* *No calls for testing were issued this week.*
83+
84+
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
85+
* *No calls for testing were issued this week.*
86+
87+
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
88+
* *No calls for testing were issued this week.*
89+
90+
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
91+
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
92+
need testing.
9093

9194
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
9295

@@ -249,47 +252,36 @@ Revision range: [490b2cc0..1b3fb316](https://perf.rust-lang.org/?start=490b2cc09
249252
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
250253
are the RFCs that were approved for implementation this week:
251254

252-
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
253-
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
254-
<!-- * []() -->
255-
256-
<!--
257-
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
258-
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
259-
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
260-
-->
255+
* *No RFCs were approved this week.*
261256

262257
### Final Comment Period
263258

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

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

272265
#### Tracking Issues & PRs
273-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
274-
<!-- or if none entered FCP this week, use: -->
275-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
276-
<!-- * [disposition: ] []() -->
277-
278266
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
267+
* [disposition: merge] [Add `--doctest-compilation-args` option to add compilation flags to doctest compilation](https://github.com/rust-lang/rust/pull/128780)
279268

280269
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
270+
* [disposition: merge] [fix(cargo-rustc): stabilize higher precedence trailing flags](https://github.com/rust-lang/cargo/pull/14900)
281271

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

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

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

288281
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
289-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
290-
<!-- or if there are no new or updated RFCs this week, use: -->
291-
<!-- * *No New or Updated RFCs were created this week.* -->
292-
<!-- * [new|updated] []() -->
282+
* [new] [Drop type destructuring](https://github.com/rust-lang/rfcs/pull/3738)
283+
* [new] [#[must_use = false]](https://github.com/rust-lang/rfcs/pull/3737)
284+
* [new] [RFC: Partial Types (v3)](https://github.com/rust-lang/rfcs/pull/3736)
293285

294286
## Upcoming Events
295287

0 commit comments

Comments
 (0)