Skip to content

Commit 2f660fd

Browse files
authored
Merge pull request #2 from rust-lang/master
[pull] master from rust-lang:master
2 parents 9d91d30 + ce6f272 commit 2f660fd

File tree

5 files changed

+978
-79
lines changed

5 files changed

+978
-79
lines changed

content/2024-04-24-this-week-in-rust.md

Lines changed: 0 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -270,21 +270,6 @@ Revision range: [ccfcd950..a77f76e2](https://perf.rust-lang.org/?start=ccfcd950b
270270

271271
[Full report here](https://github.com/rust-lang/rustc-perf/blob/e29814aa8d206406ae2711773bd882b39598a9d8/triage/2024-04-23.md)
272272

273-
## Call for Testing
274-
An important step for RFC implementation is for people to experiment with the
275-
implementation and give feedback, especially before stabilization. The following
276-
RFCs would benefit from user testing before moving forward:
277-
278-
* *No calls for testing were issued this week.*
279-
280-
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
281-
282-
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
283-
284-
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
285-
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
286-
need testing.
287-
288273
### [Approved RFCs](https://github.com/rust-lang/rfcs/commits/master)
289274

290275
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These

0 commit comments

Comments
 (0)