There should be a way to filter which packages in a workspace are built.

[eddyb]

I work on Rust-GPU nowadays, and specifically the rustc_codegen_spirv crate in it, but that has a bunch of downstream users in the same workspace, so right now I have to wait for RLS to rebuild all of those every time I make a change (in rustc_codegen_spirv).

Neither "rust.all_targets": false nor "rust.build_lib": true seem to do their job (see #1715), but even if they did, they wouldn't full solve the problem, which is that there's no fine-grained control over which packages should be rebuilt.

The "rust.crate_blacklist" option exists, but it doesn't do what one might naively expect, and it should be documented as specifically not skipping building, just skipping save-analysis (presumably to work around bugs in save-analysis?).

When talking to @Xanewok, he suggested a new packages setting, and I've also found #614 that might be relevant.

[eddyb]

Based on #614 I tried opening just the crates/rustc_codegen_spirv directory in VSCode, and it does only build that package!
Which is probably good enough for now, even tho I prefer opening workspace roots in VSCode, and I'll probably forget to type ../../ in some command at some point.