rust-analzyer doesn't report error

[namse]

cargo check reports errors but rust-analyzer doesn't.

vs-code with rust-analyzer

cargo check result

rust-analyzer version: 0add6e9 2021-12-20 stable

rustc version: rustc 1.56.1 (59eed8a2a 2021-11-01)

[jhgg]

Perchance, do you have checkOnSave enabled?

[gtsiam]

I've run into this too actually, though it was with nightly toolchains: Every time I updated nightly, I had to do cargo clean and restart vscode, otherwise I wouldn't see any errors.

[namse]

@jhgg

Perchance, do you have checkOnSave enabled?

Yes, it's enabled. Actually it was worked well before, but I got a trouble after put non-wasm project in my wasm project's workspace(Not very sure that is the reason of problem).

For now I deleted workspace (!?) and it works very well. Should I give up using workspace if I do wasm, non-wasm both project together?

[namse]

I was expecting rust-analzyer to tell the user why when a check fails.
The biggest problem, I think, is that rust-analyzer doesn't tell me why.
Nowhere does it tell us why rust-analyzer died. How do I know if a check is failing for some reason?

[namse]

More info!
I found that rust-analyzer hangs without any error reports if there is a build problem with the crate I added.
I use some internal crates with path import.

I hope rust-analzyer to explain to user, which crate rust-analzyer died while checking with a popup at the bottom right of vscode at least.

[Veykril]

You mean a dependency of yours failed to build right? Ye that will prevent cargo from doing anymore error checking in your workspace swallowing the errors. We should probably check if we get diagnostics in non-workspace dependencies and notify the user about that.

[Veykril]

Fixed in #11960