@@ -57,29 +57,18 @@ and just ask the editors to select the category.
57
57
[ submit_crate ] : https://users.rust-lang.org/t/crate-of-the-week/2704
58
58
59
59
## Calls for Testing
60
-
61
60
An important step for RFC implementation is for people to experiment with the
62
- implementation and give feedback, especially before stabilization. The following
63
- RFCs would benefit from user testing before moving forward:
64
-
65
- <!-- Calls for Testing go here, use this format:
66
- * [<RFC Topic>](<RFC URL>)
67
- * [Tracking Issue](<Tracking Issue URL>)
68
- * [Testing steps](<Testing Steps URL>)
69
- -->
70
- <!-- or if there are no new or updated RFCs this week, use: -->
71
- <!-- * *No New or Updated RFCs were created this week.* -->
72
- <!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
61
+ implementation and give feedback, especially before stabilization.
73
62
74
- ### [ RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing )
63
+ If you are a feature implementer and would like your RFC to appear in this list, add a
64
+ ` call-for-testing ` label to your RFC along with a comment providing testing instructions and/or
65
+ guidance on which aspect(s) of the feature need testing.
75
66
76
- ### [ Rust] ( https://github.com/rust-lang/rust/labels/call-for-testing )
67
+ * * No calls for testing were issued this week by [ Rust] ( https://github.com/rust-lang/rust/labels/call-for-testing ) ,
68
+ [ Rust language RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing ) or
69
+ [ Rustup] ( https://github.com/rust-lang/rustup/labels/call-for-testing ) .*
77
70
78
- ### [ Rustup] ( https://github.com/rust-lang/rustup/labels/call-for-testing )
79
-
80
- If you are a feature implementer and would like your RFC to appear on the above list, add the new ` call-for-testing `
81
- label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
82
- need testing.
71
+ [ 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.
83
72
84
73
## Call for Participation; projects and speakers
85
74
@@ -120,47 +109,39 @@ If you are an event organizer hoping to expand the reach of your event, please s
120
109
Changes to Rust follow the Rust [ RFC (request for comments) process] ( https://github.com/rust-lang/rfcs#rust-rfcs ) . These
121
110
are the RFCs that were approved for implementation this week:
122
111
123
- <!-- Approved RFCs go here, use this format: * [Topic](URL) -->
124
- <!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
125
- <!-- * []() -->
126
-
127
- <!--
128
- ### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
129
- <!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
130
- <!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
131
- -->
112
+ * * No RFCs were approved this week.*
132
113
133
114
### Final Comment Period
134
115
135
116
Every week, [ the team] ( https://www.rust-lang.org/team.html ) announces the 'final comment period' for RFCs and key PRs
136
117
which are reaching a decision. Express your opinions now.
137
118
138
- #### [ RFCs] ( https://github.com/rust-lang/rfcs/labels/final-comment-period )
139
- <!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
140
- <!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
141
- <!-- * [disposition: ] []() -->
142
-
143
119
#### Tracking Issues & PRs
144
- <!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
145
- <!-- or if none entered FCP this week, use: -->
146
- <!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
147
- <!-- * [disposition: ] []() -->
148
-
149
120
##### [ Rust] ( https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
121
+ * [ Allow comparisons between ` CStr ` , ` CString ` , and ` Cow<CStr> ` .] ( https://github.com/rust-lang/rust/pull/137268 )
122
+ * [ Tracking Issue for ` const_eq_ignore_ascii_case ` ] ( https://github.com/rust-lang/rust/issues/131719 )
123
+ * [ Stabilize feature result_flattening] ( https://github.com/rust-lang/rust/pull/141072 )
124
+ * [ Tracking Issue for ` breakpoint ` feature (` core::arch::breakpoint ` )] ( https://github.com/rust-lang/rust/issues/133724 )
125
+ * [ Stabilize ` sha512 ` . ` sm3 ` and ` sm4 ` for x86] ( https://github.com/rust-lang/rust/pull/140767 )
126
+ * [ Stabilize keylocker] ( https://github.com/rust-lang/rust/pull/140766 )
127
+ * [ terminology: allocated object → allocation] ( https://github.com/rust-lang/rust/pull/141224 )
128
+ * [ Tracking Issue for ` keylocker_x86 ` ] ( https://github.com/rust-lang/rust/issues/134813 )
129
+ * [ Tracking Issue for ` sha512_sm_x86 ` ] ( https://github.com/rust-lang/rust/issues/126624 )
150
130
151
131
##### [ Cargo] ( https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
132
+ * [ Use ` gix ` for ` cargo package ` ] ( https://github.com/rust-lang/cargo/pull/15534 )
152
133
153
- ##### [ Language Team] ( https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+ )
154
-
155
- ##### [ Language Reference] ( https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
134
+ * No Items entered Final Comment Period this week for
135
+ [ Rust RFCs] ( https://github.com/rust-lang/rfcs/labels/final-comment-period ) ,
136
+ [ Language Reference] ( https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) ,
137
+ [ Language Team] ( https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+ ) or
138
+ [ Unsafe Code Guidelines] ( https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc ) .*
156
139
157
- ##### [ Unsafe Code Guidelines ] ( https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
140
+ Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
158
141
159
142
#### [ New and Updated RFCs] ( https://github.com/rust-lang/rfcs/pulls )
160
- <!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
161
- <!-- or if there are no new or updated RFCs this week, use: -->
162
- <!-- * *No New or Updated RFCs were created this week.* -->
163
- <!-- * [new|updated] []() -->
143
+ * [ new] [ RFC: Changes to target_feature attribute] ( https://github.com/rust-lang/rfcs/pull/3820 )
144
+ * [ new] [ RFC: Promote aarch64-pc-windows-msvc to Tier 1] ( https://github.com/rust-lang/rfcs/pull/3817 )
164
145
165
146
## Upcoming Events
166
147
0 commit comments