Skip to content

Commit 630d461

Browse files
U007DU007D
committed
Update RFC, MCP, FCP and CFT sections for TWiR-588
1 parent 61b7895 commit 630d461

File tree

1 file changed

+30
-55
lines changed

1 file changed

+30
-55
lines changed

‎draft/2025-02-26-this-week-in-rust.md‎

Lines changed: 30 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -54,29 +54,19 @@ 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
59-
implementation and give feedback, especially before stabilization. The following
60-
RFCs would benefit from user testing before moving forward:
61-
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. -->
58+
implementation and give feedback, especially before stabilization.
7059

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

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

75-
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
76-
77-
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
78-
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
79-
need testing.
69+
Let us know if you would like your feature to be tracked as a part of this list.
8070

8171
## Call for Participation; projects and speakers
8272

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

120-
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
121-
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
122-
<!-- * []() -->
123-
124-
<!--
125-
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
126-
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
127-
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
128-
-->
129-
130-
### Final Comment Period
131-
132-
Every week, [the team](https://www.rust-lang.org/team.html) announces the 'final comment period' for RFCs and key PRs
133-
which are reaching a decision. Express your opinions now.
134-
135-
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
136-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
137-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
138-
<!-- * [disposition: ] []() -->
110+
* [RFC: project goals for 2025h1](https://github.com/rust-lang/rfcs/pull/3764)
139111

140112
#### Tracking Issues & PRs
141-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
142-
<!-- or if none entered FCP this week, use: -->
143-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
144-
<!-- * [disposition: ] []() -->
145-
146113
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
147-
148-
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
149-
150-
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
151-
152-
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
153-
154-
##### [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
114+
* [Make `ptr_cast_add_auto_to_object lint` into hard error](https://github.com/rust-lang/rust/pull/136764)
115+
* [Tracking Issue for `const_copy_from_slice`](https://github.com/rust-lang/rust/issues/131415)
116+
* [Tracking Issue for `const_char_classify`](https://github.com/rust-lang/rust/issues/132241)
117+
* [Allow `*const W<dyn A> -> *const dyn A ptr` cast](https://github.com/rust-lang/rust/pull/136127)
118+
* [Fix parsing of ranges after unary operators](https://github.com/rust-lang/rust/pull/134900)
119+
* [Tracking issue for `slice_take`](https://github.com/rust-lang/rust/issues/62280)
120+
* [Tracking Issue for `box_uninit_write`](https://github.com/rust-lang/rust/issues/129397)
121+
122+
#### Other Areas
123+
* *No Items entered Final Comment Period this week for
124+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
125+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
126+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
127+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc) or
128+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
129+
130+
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
155131

156132
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
157-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
158-
<!-- or if there are no new or updated RFCs this week, use: -->
159-
<!-- * *No New or Updated RFCs were created this week.* -->
160-
<!-- * [new|updated] []() -->
133+
* [RFC: Add additional `inline` intents](https://github.com/rust-lang/rfcs/pull/3778)
134+
* [RFC: Add "spaceship" operator.](https://github.com/rust-lang/rfcs/pull/3776)
135+
* [Guarantee slice representation](https://github.com/rust-lang/rfcs/pull/3775)
161136

162137
## Upcoming Events
163138

0 commit comments

Comments
 (0)