Skip to content

Commit a5f8ae0

Browse files
authored
Merge pull request #5997 from U007D/master
Update RFC, MCP, FCP and CFT sections for TWiR-568
2 parents 2931064 + 2cb2dc6 commit a5f8ae0

File tree

1 file changed

+40
-39
lines changed

1 file changed

+40
-39
lines changed

draft/2024-10-09-this-week-in-rust.md

Lines changed: 40 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -68,18 +68,19 @@ llogiq is still pleased with his choice, but increasingly unhappy about the lack
6868

6969
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
7070

71-
## [Call for Testing](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
71+
## Calls for Testing
7272
An important step for RFC implementation is for people to experiment with the
7373
implementation and give feedback, especially before stabilization. The following
7474
RFCs would benefit from user testing before moving forward:
7575

76-
<!-- Calls for Testing go here, use this format:
77-
* [<RFC Topic>](<RFC URL>)
78-
* [Tracking Issue](<Tracking Issue URL>)
79-
* [Testing steps](<Testing Steps URL>)
80-
-->
81-
<!-- or if there are no new or updated RFCs this week, use: * *No New or Updated RFCs were created this week.* -->
82-
<!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
76+
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
77+
* *No calls for testing were issued this week.*
78+
79+
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
80+
* *No calls for testing were issued this week.*
81+
82+
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
83+
* *No calls for testing were issued this week.*
8384

8485
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
8586
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
@@ -227,44 +228,44 @@ Revision range: [c87004a1..e6c46db4](https://perf.rust-lang.org/?start=c87004a1f
227228
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
228229
are the RFCs that were approved for implementation this week:
229230

230-
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
231-
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
232-
<!-- * []() -->
233-
234-
<!--
235-
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
236-
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
237-
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
238-
-->
231+
* [RFC: Allow boolean literals as `cfg` predicates](https://github.com/rust-lang/rfcs/pull/3695)
232+
* [Move `rustdoc-types` crate to T-Rustdoc ownership.](https://github.com/rust-lang/rfcs/pull/3505)
239233

240234
### Final Comment Period
241235

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

245239
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
246-
247-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
248-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
249-
<!-- * [disposition: ] []() -->
250-
251-
#### [Tracking Issues & PRs](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
252-
253-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
254-
<!-- or if none entered FCP this week, use: * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
255-
<!-- * [disposition: ] []() -->
256-
257-
### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
258-
<!-- Remove this section if empty>
259-
260-
### [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
261-
<!-- Remove this section if empty>
262-
263-
### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
264-
265-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
266-
<!-- or if there are no new or updated RFCs this week, use: * *No New or Updated RFCs were created this week.* -->
267-
<!-- * [new|updated] []() -->
240+
* *No RFCs entered Final Comment Period this week.*
241+
242+
#### Tracking Issues & PRs
243+
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
244+
* [disposition: merge] [Stabilize const `ptr::write*` and `mem::replace`](https://github.com/rust-lang/rust/pull/130954)
245+
* [disposition: merge] [Check ABI target compatibility for function pointers](https://github.com/rust-lang/rust/pull/128784)
246+
* [disposition: merge] [Proposal: stabilize `if_let_rescope` for Edition 2024](https://github.com/rust-lang/rust/issues/131154)
247+
* [disposition: merge] [Fixup Windows verbatim paths when used with the `include!` macro](https://github.com/rust-lang/rust/pull/125205)
248+
* [disposition: merge] [Implemented `FromStr` for `CString` and `TryFrom<CString>` for `String`](https://github.com/rust-lang/rust/pull/130608)
249+
* [disposition: merge] [Tracking Issue for `debug_more_non_exhaustive`](https://github.com/rust-lang/rust/issues/127942)
250+
* [disposition: merge] [Tracking Issue for `const_make_ascii`](https://github.com/rust-lang/rust/issues/130698)
251+
* [disposition: merge] [Tracking Issue for `const_char_encode_utf8`](https://github.com/rust-lang/rust/issues/130512)
252+
253+
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
254+
* [disposition: merge] [feat: Stabilize MSRV-aware resolver config](https://github.com/rust-lang/cargo/pull/14639)
255+
* [disposition: merge] [Official API for build scripts](https://github.com/rust-lang/cargo/issues/12432)
256+
257+
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
258+
* [disposition: merge] [Meeting proposal: rename "object safety" to "dyn compatibility"](https://github.com/rust-lang/lang-team/issues/286)
259+
260+
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
261+
* *No Language Reference RFCs entered Final Comment Period this week.*
262+
263+
##### [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
264+
* *No Unsafe Code Guideline Tracking Issues or PRs entered Final Comment Period this week.*
265+
266+
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
267+
* [new] [RFC: Promote riscv64gc-unknown-linux-gnu to Tier-1 (without host tools)](https://github.com/rust-lang/rfcs/pull/3707)
268+
* [new] [[RFC] Add Option::todo and Result::todo](https://github.com/rust-lang/rfcs/pull/3706)
268269

269270
## Upcoming Events
270271

0 commit comments

Comments
 (0)