Skip to content

Commit 7923734

Browse files
authored
Merge pull request #6678 from U007D/master
Update RFC, MCP, FCP and CFT sections for TWiR-601
2 parents 179e7cb + 61e1c25 commit 7923734

File tree

1 file changed

+27
-46
lines changed

1 file changed

+27
-46
lines changed

draft/2025-05-28-this-week-in-rust.md

Lines changed: 27 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -62,29 +62,18 @@ and just ask the editors to select the category.
6262
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
6363

6464
## Calls for Testing
65-
6665
An important step for RFC implementation is for people to experiment with the
67-
implementation and give feedback, especially before stabilization. The following
68-
RFCs would benefit from user testing before moving forward:
69-
70-
<!-- Calls for Testing go here, use this format:
71-
* [<RFC Topic>](<RFC URL>)
72-
* [Tracking Issue](<Tracking Issue URL>)
73-
* [Testing steps](<Testing Steps URL>)
74-
-->
75-
<!-- or if there are no new or updated RFCs this week, use: -->
76-
<!-- * *No New or Updated RFCs were created this week.* -->
77-
<!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
66+
implementation and give feedback, especially before stabilization.
7867

79-
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
68+
If you are a feature implementer and would like your RFC to appear in this list, add a
69+
`call-for-testing` label to your RFC along with a comment providing testing instructions and/or
70+
guidance on which aspect(s) of the feature need testing.
8071

81-
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
72+
* *No calls for testing were issued this week by [Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
73+
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) or
74+
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
8275

83-
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
84-
85-
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
86-
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
87-
need testing.
76+
[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.
8877

8978
## Call for Participation; projects and speakers
9079

@@ -125,47 +114,39 @@ If you are an event organizer hoping to expand the reach of your event, please s
125114
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
126115
are the RFCs that were approved for implementation this week:
127116

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

138119
### Final Comment Period
139120

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

143-
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
144-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
145-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
146-
<!-- * [disposition: ] []() -->
147-
148124
#### Tracking Issues & PRs
149-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
150-
<!-- or if none entered FCP this week, use: -->
151-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
152-
<!-- * [disposition: ] []() -->
153-
154125
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
126+
* [Allow comparisons between `CStr`, `CString`, and `Cow<CStr>`.](https://github.com/rust-lang/rust/pull/137268)
127+
* [Tracking Issue for `const_eq_ignore_ascii_case`](https://github.com/rust-lang/rust/issues/131719)
128+
* [Stabilize feature result_flattening](https://github.com/rust-lang/rust/pull/141072)
129+
* [Tracking Issue for `breakpoint` feature (`core::arch::breakpoint`)](https://github.com/rust-lang/rust/issues/133724)
130+
* [Stabilize `sha512`. `sm3` and `sm4` for x86](https://github.com/rust-lang/rust/pull/140767)
131+
* [Stabilize keylocker](https://github.com/rust-lang/rust/pull/140766)
132+
* [terminology: allocated object → allocation](https://github.com/rust-lang/rust/pull/141224)
133+
* [Tracking Issue for `keylocker_x86`](https://github.com/rust-lang/rust/issues/134813)
134+
* [Tracking Issue for `sha512_sm_x86`](https://github.com/rust-lang/rust/issues/126624)
155135

156136
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
137+
* [Use `gix` for `cargo package`](https://github.com/rust-lang/cargo/pull/15534)
157138

158-
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
159-
160-
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
139+
*No Items entered Final Comment Period this week for
140+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
141+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
142+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+) or
143+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
161144

162-
##### [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
145+
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
163146

164147
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
165-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
166-
<!-- or if there are no new or updated RFCs this week, use: -->
167-
<!-- * *No New or Updated RFCs were created this week.* -->
168-
<!-- * [new|updated] []() -->
148+
* [new] [RFC: Changes to target_feature attribute](https://github.com/rust-lang/rfcs/pull/3820)
149+
* [new] [RFC: Promote aarch64-pc-windows-msvc to Tier 1](https://github.com/rust-lang/rfcs/pull/3817)
169150

170151
## Upcoming Events
171152

0 commit comments

Comments
 (0)