Skip to content

Commit 882699e

Browse files
committed
Address Call for Testing review feedback
1 parent 2536baa commit 882699e

File tree

1 file changed

+16
-1
lines changed

1 file changed

+16
-1
lines changed

src/implementing_new_features.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -207,7 +207,19 @@ tests/ui/feature-gates/ --bless`.
207207

208208
## Call for testing
209209

210-
Once the implementation is complete, the feature will be available to nightly users, but not yet part of stable Rust. This is a good time to write a blog post on [one of the Rust blogs](https://github.com/rust-lang/blog.rust-lang.org/) and issue a call for testing (here are three [example](https://blog.rust-lang.org/2021/08/03/GATs-stabilization-push.html) [blog](https://blog.rust-lang.org/inside-rust/2024/08/09/async-closures-call-for-testing.html) [posts](https://blog.rust-lang.org/2024/09/05/impl-trait-capture-rules.html) to give you the idea). The post should highlight how the feature works, what areas you'd like people to play with, and how they can supply feedback.
210+
Once the implementation is complete, the feature will be available to nightly users, but not yet part of stable Rust. This is a good time to write a blog post on [the main Rust blog][rust-blog] and issue a **Call for Testing**.
211+
212+
Some example Call for Testing blog posts:
213+
214+
1. [The push for GATs stabilization](https://blog.rust-lang.org/2021/08/03/GATs-stabilization-push/)
215+
2. [Changes to `impl Trait` in Rust 2024](https://blog.rust-lang.org/2024/09/05/impl-trait-capture-rules.html)
216+
3. [Async Closures MVP: Call for Testing!](https://blog.rust-lang.org/inside-rust/2024/08/09/async-closures-call-for-testing/)
217+
218+
Alternatively, [*This Week in Rust*][twir] has a [call-for-testing section][twir-cft]. Example:
219+
220+
- [Call for testing on boolean literals as cfg predicates](https://github.com/rust-lang/rust/issues/131204#issuecomment-2569314526).
221+
222+
Which option to choose might depend on how significant the language change is, though note that [*This Week in Rust*][twir]'s Call for Testing section might be less visible than a dedicated post on the main Rust blog.
211223

212224
## Affiliated work
213225

@@ -223,3 +235,6 @@ Once the feature is supported by rustc, there is other associated work that need
223235
The final step in the feature lifecycle is [stabilization][stab], which is when the feature becomes available to all Rust users. At this point, backwards incompatible changes are no longer permitted (modulo soundness bugs and inference changes; see the lang team's [defined semver policies](https://rust-lang.github.io/rfcs/1122-language-semver.html) for full details). To learn more about stabilization, see the [stabilization guide][stab].
224236

225237
[stab]: ./stabilization_guide.md
238+
[rust-blog]: https://github.com/rust-lang/blog.rust-lang.org/
239+
[twir]: https://github.com/rust-lang/this-week-in-rust
240+
[twir-cft]: https://this-week-in-rust.org/blog/2025/01/22/this-week-in-rust-583/#calls-for-testing

0 commit comments

Comments
 (0)