Skip to content

docs(guide): Talk about removing unused features #16085

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.

Sign up for GitHub

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
Oct 14, 2025
Merged

docs(guide): Talk about removing unused features #16085

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0e00b14
docs(guide): Switch build-perf note from italics to bold
epage Oct 10, 2025
7187b5e
docs(guide): Talk about removing unused features
epage Oct 10, 2025
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
20 changes: 19 additions & 1 deletion src/doc/src/guide/build-performance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,8 +122,26 @@ Recommendation: Periodically review unused dependencies for removal using third-
When changing code,
it can be easy to miss that a dependency is no longer used and can be removed.

> *Note:* native support for this in Cargo is being tracked in [#15813](https://github.com/rust-lang/cargo/issues/15813).
> **Note:** native support for this in Cargo is being tracked in [#15813](https://github.com/rust-lang/cargo/issues/15813).

Trade-offs:
- ✅ Faster full build and link times
- ❌ May incorrectly flag dependencies as unused or miss some

### Removing unused features from dependencies

Recommendation: Periodically review unused features from dependencies for removal using third-party tools like
[cargo-features-manager](https://crates.io/crates/cargo-features-manager),
[cargo-unused-features](https://crates.io/crates/cargo-unused-features).

When changing code,
it can be easy to miss that a dependency's feature is no longer used and can be removed.
This can reduce the number of transitive dependencies being built or
reduce the amount of code within a crate being built.
When removing features, extra caution is needed because features
may also be used for desired behavior or performance changes
which may not always be obvious from compiling or testing.

Trade-offs:
- ✅ Faster full build and link times
- ❌ May incorrectly flag features as unused