Open matthiaskrgr opened 5 years ago
What would you expect sccache to do in this scenario? AFAIK rls and clippy aren't performing actual compilation so there isn't likely to be any benefit from caching the executions.
rls calls rustc and dumps its compilation output into target/rls
.
clippy-driver also calls rustc, but none of these calls (both clippy and rls) seem to be cached.
I was trying to play around with the code and make it accept "clippy-driver rustc" as a valid "compiler" but to no avail.
I'm not sure about clippy but as for rls, I think it does benefit from having RUSTC_WRAPPER="sccache"
set in the environment.
As a workaround for clippy, it's possible to run check before as both use the same (rustc managed-)cache. On some project of mine, running clippy directly takes ~4m10s, but running cargo check && cargo clippy
takes only ~2m30 by taking advantage of sccache
It's possible this was fixed by #441
Similar discussion: https://github.com/mozilla/sccache/issues/539
It would be great if sccache supported clippy and rls calls as well. I tried something like
RUSTC_WRAPPER="sccache clippy-driver rustc"
but that didn't work out.