@@ -54,19 +54,23 @@ and just ask the editors to select the category.
54
54
[ submit_crate ] : https://users.rust-lang.org/t/crate-of-the-week/2704
55
55
56
56
## Calls for Testing
57
-
58
57
An important step for RFC implementation is for people to experiment with the
59
58
implementation and give feedback, especially before stabilization. The following
60
59
RFCs would benefit from user testing before moving forward:
61
60
62
- <!-- Calls for Testing go here, use this format:
63
- * [<RFC Topic>](<RFC URL>)
64
- * [Tracking Issue](<Tracking Issue URL>)
65
- * [Testing steps](<Testing Steps URL>)
66
- -->
67
- <!-- or if there are no new or updated RFCs this week, use: -->
68
- <!-- * *No New or Updated RFCs were created this week.* -->
69
- <!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
61
+ ### [ RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing )
62
+ * * No calls for testing were issued this week.*
63
+
64
+ ### [ Rust] ( https://github.com/rust-lang/rust/labels/call-for-testing )
65
+ * [ Tracking issue for RFC 3695: Allow boolean literals as cfg predicates] ( https://github.com/rust-lang/rust/issues/131204 )
66
+ - [ Testing steps] ( https://github.com/rust-lang/rust/issues/131204#issuecomment-2569314526 )
67
+
68
+ ### [ Rustup] ( https://github.com/rust-lang/rustup/labels/call-for-testing )
69
+ * * No calls for testing were issued this week.*
70
+
71
+ If you are a feature implementer and would like your RFC to appear on the above list, add the new ` call-for-testing `
72
+ label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
73
+ need testing.
70
74
71
75
### [ RFCs] ( https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing )
72
76
@@ -117,47 +121,37 @@ If you are an event organizer hoping to expand the reach of your event, please s
117
121
Changes to Rust follow the Rust [ RFC (request for comments) process] ( https://github.com/rust-lang/rfcs#rust-rfcs ) . These
118
122
are the RFCs that were approved for implementation this week:
119
123
120
- <!-- Approved RFCs go here, use this format: * [Topic](URL) -->
121
- <!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
122
- <!-- * []() -->
123
-
124
- <!--
125
- ### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
126
- <!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
127
- <!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
128
- -->
124
+ * * No RFCs were approved this week.*
129
125
130
126
### Final Comment Period
131
127
132
128
Every week, [ the team] ( https://www.rust-lang.org/team.html ) announces the 'final comment period' for RFCs and key PRs
133
129
which are reaching a decision. Express your opinions now.
134
130
135
131
#### [ RFCs] ( https://github.com/rust-lang/rfcs/labels/final-comment-period )
136
- <!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
137
- <!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
138
- <!-- * [disposition: ] []() -->
132
+ * [ Explicit ABIs in extern] ( https://github.com/rust-lang/rfcs/pull/3722 )
139
133
140
134
#### Tracking Issues & PRs
141
- <!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
142
- <!-- or if none entered FCP this week, use: -->
143
- <!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
144
- <!-- * [disposition: ] []() -->
145
-
146
135
##### [ Rust] ( https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
136
+ * [ Tracking Issue for ` float_next_up_down ` ] ( https://github.com/rust-lang/rust/issues/91399 )
137
+ * [ Impl TryFrom<Vec<u8 >> for String] ( https://github.com/rust-lang/rust/pull/132268 )
138
+ * [ Tracking Issue for anonymous pipe API] ( https://github.com/rust-lang/rust/issues/127154 )
139
+ * [ Convert ` struct FromBytesWithNulError ` into enum] ( https://github.com/rust-lang/rust/pull/134143 )
147
140
148
141
##### [ Cargo] ( https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
142
+ * [ simplify SourceID Ord/Eq] ( https://github.com/rust-lang/cargo/pull/14980 )
149
143
150
144
##### [ Language Team] ( https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+ )
145
+ * * No Language Team Proposals entered Final Comment Period this week.*
151
146
152
147
##### [ Language Reference] ( https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
148
+ * * No Language Reference RFCs entered Final Comment Period this week.*
153
149
154
150
##### [ Unsafe Code Guidelines] ( https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc )
151
+ * * No Unsafe Code Guideline Tracking Issues or PRs entered Final Comment Period this week.*
155
152
156
153
#### [ New and Updated RFCs] ( https://github.com/rust-lang/rfcs/pulls )
157
- <!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
158
- <!-- or if there are no new or updated RFCs this week, use: -->
159
- <!-- * *No New or Updated RFCs were created this week.* -->
160
- <!-- * [new|updated] []() -->
154
+ * * No New or Updated RFCs were created this week.*
161
155
162
156
## Upcoming Events
163
157
0 commit comments