How to ignore certain crates in a workspace

[rbalicki2]

Is it possible to have the RLS vscode extension disabled for a particular crate in a workspace? I don't know why, but it always hangs in a particular crate which contains tests for a procedural macro. Nothing depends on this crate, thankfully.

Removing it from the top-level cargo.toml workspace.members array works. Interestingly, when I modify and save the smd_tests crate, RLS recompiles that folder and just works!

both cargo +nightly build and cd smd_tests && cargo +nightly test work.

Thank you!

Specific info

The repository in which this is broken is
https://github.com/rbalicki2/smithy.
See 00c789cf05e1c190567ccf83fb053863ad38a380 for a broken commit, and 0b66edee1e4e176795bab90ed442b91a88832143 for a commit in which smd_tests is in its own sub-workspace.

My only settings are

    "rust-client.revealOutputChannelOn": "warn",
    "rust.all_targets": false     // broken with both true and false

If rust.all_targets is false, it hangs on RLS [building]. If it's removed, it hangs on RLS (spinner) smd_tests cfg[test]

active toolchain

nightly-x86_64-apple-darwin (default)
rustc 1.32.0-nightly (6b9b97bd9 2018-11-15)

[Xanewok]

Unfortunately handling procedural macros isn't in the best place right now - ideally we'd need to isolate compilation/analysis to a separate process (currently RLS prefers to do everything in-process). I'll take a look at the proc macro example.