-
Notifications
You must be signed in to change notification settings - Fork 1.8k
internal: Utilize cargo check --compile-time-deps
#20047
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
Conversation
😍 |
Do we want to disable |
We should not set the wrapper if we use the flag |
4740f65
to
98c92fa
Compare
Oh, I missed it. Thanks! |
This is amazing, can't wait to get rid of the wrapper in the future |
Does this work in the rust-lang/rust workspace too? |
Haven't tested in it yet but I guess so? |
We set |
Oh, I forgot about those So, adding supports for |
Opened rust-lang/rust#143785. Saves a lot of time! |
That's way better than my naive expectations 🎉 |
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