orlp
Reputation: 117771
How to find dead code in a cargo workspace?
Rust will helpfully warn you if you have non-public functions or other items that are never used in the crate. This is great when developing a single crate, but has issues when you split your program up in multiple crates in a workspace.
Is there a way to automatically find dead code across multiple crates in a workspace? Ideally I'd be able to mark one crate in the workspace as a 'main' crate, and then every item which does not end up (indirectly) being used in the main crate (even if it is pub) is warned about as being unused.
Upvotes: 2
Views: 49
Answers (0)
Related Questions
- How do you disable dead code warnings at the crate level in Rust?
- Does cargo install have an equivalent update command?
- Cargo build hangs with " Blocking waiting for file lock on the registry index" after building parity from source
- Is there a command to update Cargo to the latest official release?
- How to add local package to local registry in Cargo?
- How can a Rust program access metadata from its Cargo package?
- Rust dead code analysis for code exposed only to the binary in the same lib crate
- How can I build multiple binaries with Cargo?
- How can I get the compiler to warn me of unused code that is marked pub?