Skip to content

Commit

Permalink
Merge pull request #4727 from U007D/twir-513
Browse files Browse the repository at this point in the history
Update RFC, MCP, FCP and CFT sections for TWiR-513
  • Loading branch information
mariannegoldin authored Sep 20, 2023
2 parents 1d8cdb5 + 9dd0300 commit feccc16
Showing 1 changed file with 10 additions and 27 deletions.
37 changes: 10 additions & 27 deletions draft/2023-09-20-this-week-in-rust.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,15 +90,7 @@ Revision range: [7e0261e7ea..af78bae](https://perf.rust-lang.org/?start=7e0261e7
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

Expand All @@ -107,34 +99,25 @@ 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: ] []() -->
* [disposition: merge] [RFC: Unicode and escape codes in literals](https://github.com/rust-lang/rfcs/pull/3349)

#### [Tracking Issues & PRs](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)

<!-- 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: ] []() -->
* [disposition: merge] [stabilize combining +bundle and +whole-archive link modifiers](https://github.com/rust-lang/rust/pull/113301)
* [disposition: merge] [Stabilize `impl_trait_projections`](https://github.com/rust-lang/rust/pull/115659)
* [disposition: merge] [Tracking Issue for `option_as_slice`](https://github.com/rust-lang/rust/issues/108545)
* [disposition: merge] [Amend style guide section for formatting where clauses in type aliases](https://github.com/rust-lang/rust/pull/114901)
* [disposition: merge] [Add allow-by-default lint for unit bindings](https://github.com/rust-lang/rust/pull/112380)

### [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] []() -->
* [new] [RFC: Remove implicit features in a new edition](https://github.com/rust-lang/rfcs/pull/3491)
* [new] [RFC: const functions in traits](https://github.com/rust-lang/rfcs/pull/3490)

### [Call for Testing](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-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:

<!-- 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. -->
* *No RFCs issued a call for testing this week.*

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
Expand Down

0 comments on commit feccc16

Please sign in to comment.