@@ -95,46 +95,17 @@ If you are a feature implementer and would like your RFC to appear in this list,
9595` call-for-testing ` label to your RFC along with a comment providing testing instructions and/or
9696guidance on which aspect(s) of the feature need testing.
9797
98- <!-- If there are new CfT items this week, include:
98+ ### [ Cargo ] ( https://github.com/rust-lang/cargo/labels/call-for-testing )
9999
100- [Repo Name](Repo URL)
101- * [<Feature name>](<Feature URL>)
102- * [Testing steps](<Testing Steps URL>)
100+ * [ Tracking Issue for timing report SVG render backend] ( https://github.com/rust-lang/cargo/issues/16440 )
103101
104- - and make note in the item so the authors know to remove the `call-for-testing` label:
105- This RFC will appear in the **Call for Testing** section of the next issue (#) of This Week in Rust (TWiR).
106- 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.
107-
108- - where `Repo Name` and `Repo URL` are one of:
102+ * No calls for testing were issued this week by
109103[ Rust] ( https://github.com/rust-lang/rust/labels/call-for-testing ) ,
110- [Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
111- [Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
112- [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
113-
114- - and `Testing steps` points directly to the procedures the item wants users to exercise.
115-
116- - For all `Repo Names` with no new CfT items this week: use (removing the repos for which new
117- CfT items did appear, of course)
118-
119- * *No calls for testing were issued this week by
120- [Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
121- [Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
122- [Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
123- [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
124- -->
104+ [ Rustup] ( https://github.com/rust-lang/rustup/labels/call-for-testing ) or
105+ [ Rust language RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing ) .*
125106
126107[ 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.
127108
128- ### [ RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing )
129-
130- ### [ Rust] ( https://github.com/rust-lang/rust/labels/call-for-testing )
131-
132- ### [ Rustup] ( https://github.com/rust-lang/rustup/labels/call-for-testing )
133-
134- If you are a feature implementer and would like your RFC to appear on the above list, add the new ` call-for-testing `
135- label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
136- need testing.
137-
138109## Call for Participation; projects and speakers
139110
140111### CFP - Projects
@@ -194,55 +165,62 @@ Revision range: [3d087e60..ebf13cca](https://perf.rust-lang.org/?start=3d087e604
194165
195166Changes to Rust follow the Rust [ RFC (request for comments) process] ( https://github.com/rust-lang/rfcs#rust-rfcs ) . These
196167are the RFCs that were approved for implementation this week:
197-
198- <!-- Use either
199- * [Item title](Item URL)
200- - or
201- * *No RFCs were approved this week.*
202- -->
168+ * [ Trait method impl restrictions (` final ` methods)] ( https://github.com/rust-lang/rfcs/pull/3678 )
169+ * [ RFC: ` #[export_visibility = ...] ` attribute] ( https://github.com/rust-lang/rfcs/pull/3834 )
203170
204171### Final Comment Period
205172
206173Every week, [ the team] ( https://www.rust-lang.org/team.html ) announces the 'final comment period' for RFCs and key PRs
207174which are reaching a decision. Express your opinions now.
208175
209176#### Tracking Issues & PRs
210- <!-- Either remove the group from the "No Items Entered Final Comment Period this week for" section
211- and add the item(s) which entered Final comment period:
212- ##### [Group](Group URL)
213- * [Item title](Item URL)
214- - for `disposition-merge` `final-comment-period` items, or
215- * [disposition: postpone]
216- - for `disposition-postpone` `final-comment-period` items, or
217- * [disposition: close]
218- - for `disposition-close` `final-comment-period` items,
219- * [disposition: unspecified]
220- - when `disposition` is unspecified or ensure the group is a part of the
221- "No Items Entered Final Comment Period this week for" section
177+ ##### [ 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 )
178+
179+ * [ Proposal for a dedicated test suite for the parallel frontend] ( https://github.com/rust-lang/compiler-team/issues/906 )
180+ * [ Promote tier 3 riscv32 ESP-IDF targets to tier 2] ( https://github.com/rust-lang/compiler-team/issues/864 )
181+ * [ Proposal for Adapt Stack Protector for Rust] ( https://github.com/rust-lang/compiler-team/issues/841 )
182+ * [ Give integer literals a sign instead of relying on negation expressions] ( https://github.com/rust-lang/compiler-team/issues/835 )
183+ * [ Also enable ICE file dumps on stable] ( https://github.com/rust-lang/compiler-team/issues/809 )
184+ * [ New Tier-3 target proposal: loongarch64-linux-android] ( https://github.com/rust-lang/compiler-team/issues/806 )
185+
186+ ##### [ Rust] ( https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
187+
188+ * [ Stabilize ` core::hint::cold_path ` ] ( https://github.com/rust-lang/rust/pull/151576 )
189+ * [ Tracking Issue for minimal const ` ControlFlow ` methods (` min_const_control_flow ` )] ( https://github.com/rust-lang/rust/issues/148738 )
190+ * [ Tracking Issue for ` new_range_api ` (part of RFC 3550)] ( https://github.com/rust-lang/rust/issues/125687 )
191+ * [ Stabilize ` assert_matches ` ] ( https://github.com/rust-lang/rust/pull/137487 )
192+ * [ resolve: Report more visibility-related early resolution ambiguities for imports] ( https://github.com/rust-lang/rust/pull/149596 )
193+ * [ Add FCW for derive helper attributes that will conflict with built-in attributes] ( https://github.com/rust-lang/rust/pull/151152 )
194+ * [ Constify ` fmt::from_fn ` ] ( https://github.com/rust-lang/rust/pull/150300 )
195+ * [ Feature-gate ` mut ref ` patterns in struct pattern field shorthand] ( https://github.com/rust-lang/rust/pull/151102 )
196+ * [ Tracking Issue for raw-pointer-to-reference conversion methods] ( https://github.com/rust-lang/rust/issues/122034 )
197+ * [ implement PartialEq\< Vec\< U\>\> for \[ T; N\] and &\[ T; N\] ] ( https://github.com/rust-lang/rust/pull/149045 )
198+ * [ thread::scope: document how join interacts with TLS destructors] ( https://github.com/rust-lang/rust/pull/149482 )
199+
200+ #### [ Cargo] ( https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
201+
202+ * [ docs(report): enhance man pages for ` cargo report * ` ] ( https://github.com/rust-lang/cargo/pull/16430 )
203+
204+ #### [ Language Reference] ( https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
205+
206+ * [ Guarantee repr(C) union field offset] ( https://github.com/rust-lang/reference/pull/2128 )
207+
222208* No Items entered Final Comment Period this week for
223- [Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
224- [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
225- [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),
226- [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
227- [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
228- [Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period) or
229- [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
209+ [ Rust RFCs] ( https://github.com/rust-lang/rfcs/labels/final-comment-period ) ,
210+ [ Leadership Council] ( https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period ) ,
211+ [ Language Team] ( https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+ ) or
212+ [ Unsafe Code Guidelines] ( https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) .*
230213
231214Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
232- -->
233215
234216#### [ New and Updated RFCs] ( https://github.com/rust-lang/rfcs/pulls )
235- <!-- Use either
236- * [Item title](Item URL)
237- - for new items, or
238- * [updated] [Item title](Item URL)
239- - for updated items, or
240- * *No New or Updated RFCs were created this week.*
241- -->
242217
243- <!-- Sample commit message
244- Update CFT, FCP, MCP and RFC sections for TWiR-xxx
245- -->
218+ * [ RFC: Natural Method Disambiguation] ( https://github.com/rust-lang/rfcs/pull/3913 )
219+ * [ Add ` derive(Deref) ` RFC] ( https://github.com/rust-lang/rfcs/pull/3911 )
220+ * [ Abi Descriptors] ( https://github.com/rust-lang/rfcs/pull/3910 )
221+ * [ Cargo mTLS registry authentication] ( https://github.com/rust-lang/rfcs/pull/3907 )
222+ * [ Let ` Option ` derive ` #[must_use] ` ] ( https://github.com/rust-lang/rfcs/pull/3906 )
223+ * [ Version-typed cfgs] ( https://github.com/rust-lang/rfcs/pull/3905 )
246224
247225## Upcoming Events
248226
0 commit comments