dnrops
/
this-week-in-rust
mirror of https://github.com/rust-lang/this-week-in-rust
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update RFC, MCP, FCP and CFT sections for TWiR-606; Update `DRAFT_TEMPLATE` for RFC, MCP, FCP and CFT (#6780) 

* Update `DRAFT_TEMPLATE` for RFC, MCP, FCP and CFT

* Update RFC, MCP, FCP and CFT sections for TWiR-606
This commit is contained in:
Brad Gibson 2025-07-02 18:44:21 -07:00 committed by GitHub
parent 01474800ec
commit d9242a3210
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 58 additions and 55 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

72
draft/2025-07-02-this-week-in-rust.md
View File

@ -66,29 +66,19 @@ Thanks to [Zeon](https://users.rust-lang.org/t/crate-of-the-week/2704/1448) for
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
## Calls for Testing
An important step for RFC implementation is for people to experiment with the
implementation and give feedback, especially before stabilization. The following
RFCs would benefit from user testing before moving forward:
implementation and give feedback, especially before stabilization.
<!-- Calls for Testing go here, use this format:
* [<RFC Topic>](<RFC URL>)
* [Tracking Issue](<Tracking Issue URL>)
* [Testing steps](<Testing Steps URL>)
-->
<!-- or if there are no new or updated RFCs this week, use: -->
<!-- * *No New or Updated RFCs were created this week.* -->
<!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
If you are a feature implementer and would like your RFC to appear in this list, add a
`call-for-testing` label to your RFC along with a comment providing testing instructions and/or
guidance on which aspect(s) of the feature need testing.
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
* *No calls for testing were issued this week by [Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
need testing.
[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.
## Call for Participation; projects and speakers
@ -190,47 +180,37 @@ Revision range: [42245d34..ad3b7257](https://perf.rust-lang.org/?start=42245d34d
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
are the RFCs that were approved for implementation this week:
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
<!-- * []() -->
<!--
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
-->
* *No RFCs were approved this week.*
### Final Comment Period
Every week, [the team](https://www.rust-lang.org/team.html) announces the 'final comment period' for RFCs and key PRs
which are reaching a decision. Express your opinions now.
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
<!-- * [disposition: ] []() -->
#### Tracking Issues & PRs
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
<!-- or if none entered FCP this week, use: -->
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
<!-- * [disposition: ] []() -->
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
* [disposition: close] [Draft: Make into_parts methods on Vec associated functions](https://github.com/rust-lang/rust/pull/141509)
* [Implement `Debug` for `EncodeWide`](https://github.com/rust-lang/rust/pull/140153)
* [If `HOME` is empty, use the fallback instead](https://github.com/rust-lang/rust/pull/141840)
* [Tracking Issue for duration_constructors_lite](https://github.com/rust-lang/rust/issues/140881)
* [Print thread ID in panic message](https://github.com/rust-lang/rust/pull/115746)
##### [Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
* [RFC: enable `derive(From)` for single-field structs](https://github.com/rust-lang/rfcs/pull/3809)
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
* [Add `[hints]` table in `Cargo.toml`, and a `hints.mostly-unused` hint](https://github.com/rust-lang/cargo/pull/15673)
* [feat(publish): Stabilize multi-package publishing](https://github.com/rust-lang/cargo/pull/15636)
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
*No Items entered Final Comment Period this week for
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+) or
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
##### [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
<!-- or if there are no new or updated RFCs this week, use: -->
<!-- * *No New or Updated RFCs were created this week.* -->
<!-- * [new|updated] []() -->
* *No New or Updated RFCs were created this week.*
## Upcoming Events

41
draft/DRAFT_TEMPLATE
View File

@ -57,19 +57,42 @@ and just ask the editors to select the category.
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
## Calls for Testing
An important step for feature implementation is for people to experiment with the
implementation and give feedback, especially before stabilization.
An important step for RFC implementation is for people to experiment with the
implementation and give feedback, especially before stabilization. The following
RFCs would benefit from user testing before moving forward:
If you are a feature implementer and would like your feature to appear in this list, add a
`call-for-testing` label to your RFC along with a comment providing testing instructions and/or
guidance on which aspect(s) of the feature need testing.
<!-- Calls for Testing go here, use this format:
* [<RFC Topic>](<RFC URL>)
* [Tracking Issue](<Tracking Issue URL>)
<!-- If there are new CfT items this week, use: -->
<!--
[Repo Name](Repo URL)
* [<Feature name>](<Feature URL>)
* [Testing steps](<Testing Steps URL>)
-->
<!-- or if there are no new or updated RFCs this week, use: -->
<!-- * *No New or Updated RFCs were created this week.* -->
<!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
<!-- where `Repo Name` and `Repo URL` are one of:
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
-->
<!-- For all `Repo Names` with no new CfT items this week: use (removing the repos for which new
CfT items did appear, of course) -->
<!--
* *No calls for testing were issued this week by
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
-->
* *No calls for testing were issued this week by [Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
[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.
-->
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)