internal: Utilize cargo check --compile-time-deps
#20047
Merged
+24
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
rust-lang/cargo#15674 has been merged and I guess it would be available in toolchain
1.90.0
I've tested this on rust-analyzer itself with cargo binary built from current master with the following my rust-analyzer branch
https://github.com/ShoyuVanilla/rust-analyzer/tree/comp-time-deps-test
and these are the results (I had run
cargo clean
before each run and modified the code a bit to use--compile-time-deps
with injected cargo binary path iff env var$CARGO_BIN_FOR_TEST
is set)With
--compile-time-deps
Without
--compile-time-deps
Comparison
analysis-stat
resultstarget
dir size--compile-time-deps
System Information