@@ -77,50 +77,18 @@ If you are a feature implementer and would like your RFC to appear in this list,
7777` call-for-testing ` label to your RFC along with a comment providing testing instructions and/or
7878guidance on which aspect(s) of the feature need testing.
7979
80- <!-- If there are new CfT items this week, include:
81-
82- [Repo Name](Repo URL)
83- * [<Feature name>](<Feature URL>)
84- * [Testing steps](<Testing Steps URL>)
85-
86- - and make note in the item so the authors know to remove the `call-for-testing` label:
87- This RFC will appear in the **Call for Testing** section of the next issue (#) of This Week in Rust (TWiR).
88- You may remove the `call-for-testing` label. Please feel free to leave the `call-for-testing` label in place if you would like this RFC to appear again in another issue of TWiR.
89-
90- - where `Repo Name` and `Repo URL` are one of:
91- [Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
92- [Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
93- [Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
94- [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
95-
96- - and `Testing steps` points directly to the procedures the item wants users to exercise.
97-
98- - For all `Repo Names` with no new CfT items this week: use (removing the repos for which new
99- CfT items did appear, of course)
100-
10180* * No calls for testing were issued this week by
10281 [ Rust] ( https://github.com/rust-lang/rust/labels/call-for-testing ) ,
103- [Rust language RFCs ](https://github.com/rust-lang/rfcs/issues?q=label%3Acall -for-testing),
104- [Cargo ](https://github.com/rust-lang/cargo/labels/call -for-testing) or
82+ [ Cargo ] ( https://github.com/rust-lang/cargo/labels/call -for-testing ) ,
83+ [ Rust language RFCs ] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall -for-testing ) or
10584 [ Rustup] ( https://github.com/rust-lang/rustup/labels/call-for-testing ) .*
106- -->
10785
10886[ 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.
10987
110- ### [ RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing )
111-
112- ### [ Rust] ( https://github.com/rust-lang/rust/labels/call-for-testing )
113-
114- ### [ Rustup] ( https://github.com/rust-lang/rustup/labels/call-for-testing )
115-
116- If you are a feature implementer and would like your RFC to appear on the above list, add the new ` call-for-testing `
117- label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
118- need testing.
119-
12088## Call for Participation; projects and speakers
12189
12290### CFP - Projects
123-
91+
12492Always wanted to contribute to open-source projects but did not know where to start?
12593Every week we highlight some tasks from the Rust community for you to pick and get started!
12694
@@ -164,54 +132,49 @@ See the [full report](https://github.com/rust-lang/rustc-perf/blob/master/triage
164132Changes to Rust follow the Rust [ RFC (request for comments) process] ( https://github.com/rust-lang/rfcs#rust-rfcs ) . These
165133are the RFCs that were approved for implementation this week:
166134
167- <!-- Use either
168- * [Item title](Item URL)
169- - or
170- * *No RFCs were approved this week.*
171- -->
135+ * * No RFCs entered Final Comment Period this week.*
172136
173137### Final Comment Period
174138
175139Every week, [ the team] ( https://www.rust-lang.org/team.html ) announces the 'final comment period' for RFCs and key PRs
176140which are reaching a decision. Express your opinions now.
177141
178142#### Tracking Issues & PRs
179- <!-- Either remove the group from the "No Items Entered Final Comment Period this week for" section
180- and add the item(s) which entered Final comment period:
181- ##### [Group](Group URL)
182- * [Item title](Item URL)
183- - for `disposition-merge` `final-comment-period` items, or
184- * [disposition: postpone]
185- - for `disposition-postpone` `final-comment-period` items, or
186- * [disposition: close]
187- - for `disposition-close` `final-comment-period` items,
188- * [disposition: unspecified]
189- - when `disposition` is unspecified or ensure the group is a part of the
190- "No Items Entered Final Comment Period this week for" section
143+ ##### [ Rust] ( https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
144+ * [ don't normalize where-clauses when checking well-formedness] ( https://github.com/rust-lang/rust/pull/148477 )
145+ * [ Stabilize ` const_mul_add ` ] ( https://github.com/rust-lang/rust/pull/148052 )
146+ * [ Do not propogate unnecessary closure constraints.] ( https://github.com/rust-lang/rust/pull/148329 )
147+ * [ Not linting ` irrefutable_let_patterns ` on let chains] ( https://github.com/rust-lang/rust/pull/146832 )
148+ * [ Make closure capturing have consistent and correct behaviour around patterns] ( https://github.com/rust-lang/rust/pull/138961 )
149+
150+ [ Compiler Team] ( https://github.com/rust-lang/compiler-team/issues?q=label%3Amajor-change%20%20label%3Afinal-comment-period ) [ (MCPs only)] ( https://forge.rust-lang.org/compiler/mcp.html )
151+ * [ Use ` annotate-snippets ` as the default emitter] ( https://github.com/rust-lang/compiler-team/issues/947 )
152+ * [ Promote powerpc64-unknown-linux-musl to tier 2 with host tools] ( https://github.com/rust-lang/compiler-team/issues/946 )
153+ * [ Proposal for a dedicated test suite for the parallel frontend] ( https://github.com/rust-lang/compiler-team/issues/906 )
154+ * [ Promote tier 3 riscv32 ESP-IDF targets to tier 2] ( https://github.com/rust-lang/compiler-team/issues/864 )
155+ * [ Proposal for Adapt Stack Protector for Rust] ( https://github.com/rust-lang/compiler-team/issues/841 )
156+ * [ Give integer literals a sign instead of relying on negation expressions] ( https://github.com/rust-lang/compiler-team/issues/835 )
157+ * [ Also enable ICE file dumps on stable] ( https://github.com/rust-lang/compiler-team/issues/809 )
158+ * [ New Tier-3 target proposal: ` loongarch64-linux-android ` ] ( https://github.com/rust-lang/compiler-team/issues/806 )
159+
160+ [ Rust RFCs] ( https://github.com/rust-lang/rfcs/labels/final-comment-period )
161+ * [ Adding a crates.io Security tab] ( https://github.com/rust-lang/rfcs/pull/3872 )
162+
163+ [ Cargo] ( https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
164+ * [ feat: stabilize ` -Zconfig-include ` ] ( https://github.com/rust-lang/cargo/pull/16284 )
165+
191166* No Items entered Final Comment Period this week for
192- [Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
193- [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
194- [Compiler Team](https://github.com/rust-lang/compiler-team/issues?q=label%3Amajor-change%20%20label%3Afinal-comment-period) [(MCPs only)](https://forge.rust-lang.org/compiler/mcp.html),
195- [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
196- [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
197- [Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period) or
198- [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
167+ [ Language Team] ( https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+ ) ,
168+ [ Language Reference] ( https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) ,
169+ [ Leadership Council] ( https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period ) or
170+ [ Unsafe Code Guidelines] ( https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) .*
199171
200172Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
201- -->
202173
203174#### [ New and Updated RFCs] ( https://github.com/rust-lang/rfcs/pulls )
204- <!-- Use either
205- * [Item title](Item URL)
206- - for new items, or
207- * [updated] [Item title](Item URL)
208- - for updated items, or
209- * *No New or Updated RFCs were created this week.*
210- -->
211-
212- <!-- Sample commit message
213- Update CFT, FCP, MCP and RFC sections for TWiR-xxx
214- -->
175+ * [ Complex numbers] ( https://github.com/rust-lang/rfcs/pull/3892 )
176+ * [ RFC: Const self fields] ( https://github.com/rust-lang/rfcs/pull/3888 )
177+ * [ Create 0000-pub_use_pub_glob.md] ( https://github.com/rust-lang/rfcs/pull/3887 )
215178
216179## Upcoming Events
217180
0 commit comments