Skip to content

Note the nightly version of Rust/Cargo needed #1664

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 17, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions content/inside-rust/call-for-testing-hint-mostly-unused.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,12 @@ possible.

Applying this option to key crates you depend on (and use only a small subset
of) can provide a substantial reduction in compile time, for debug builds and
especially for release builds.
especially for release builds. The remainder of this post shows how to apply
this option selectively using Cargo, when to use it, and how it performs.

(Note that this option should *not* be applied to all crates, e.g. using
`RUSTFLAGS`. See the rest of this post for guidance on when to apply it, and
why it shouldn't be applied across the board.)

## How does this perform?

Expand Down Expand Up @@ -151,7 +156,7 @@ allow the top-level crate to override.

## How do I help?

We'd love for you to test out this feature on the latest Rust nightly compiler[^nightly].
We'd love for you to test out this feature on the latest nightly Rust and Cargo (2025-07-16 or newer)[^nightly].

[^nightly]: Make sure to run `rustup update nightly` (or however you manage your Rust releases).

Expand Down