Laurențiu Nicola

Can't we set `RA_RUSTC_WRAPPPER=$RUSTC_WRAPPER` in step 1, then we check for it (in step 5) and run that instead?

> How do you make sure that it doesn't run for rustc invoked by cargo then? Hmm... > Is that being tracked on the cargo side somewhere, are the cargo...

We could use a file to pass information from one invocation to another, but I don't think we can figure out when all the build scripts finished compiling (multiple crates...

I think it's going to matter a lot for people who disable `rust-analyzer.checkOnSave.enable`. But we can probably remove or disable it until we get some proper support in Cargo.

@jplatte that might come from the `image` crate, but I wonder why it says `all`.

I've seen some weird build errors without the proxy which got fixed after a `cargo clean`, but you might be right.

@jplatte you should probably test on a nightly which includes https://github.com/rust-lang/rust-analyzer/pull/12984/. That might help a little, but probably not as much as the wrapper.

It not always 30%, if you disable check on save, it can take arbitrarily longer depending on how large the project is, right?

We could, but the only crate which doesn't build correctly under the wrapper happens to be quite popular, so most users would have to keep it disabled.

You seem to be using VSCodium, which is why installing it directly doesn't work. Installing the VSIX might work, but I don't understand that error. Does it really say SERVERPATH?...