Alex Kladov

Original one is `cargo check --workspace --message-format=json`

That’s the base command, yeah, you need to add -p some-package no top of it to narrow it to a single package

@mvtec-bergdolll I think it's not so much "anything missing", but rather "we need to redesign one of our core abstractions to support this at all". See https://github.com/rust-lang/rust-analyzer/issues/9403.

If we have an entry for A in the linked projects, then yes, we'll find usages (or at least, will be able to find them in theory, depending on how...

>It seems like this is a problem for big workspaces, but I've often used projects where just looking into every top-level directory would be enough to discover all Cargo.tomls needed....

Yeah, that's true... I wonder if we should add a "change config" LSP extension?

Uhh 

Note: got this idea after reading "early on, we decided that syntax trees would be the basic API of Roslyn" in some blog. My first reaction was "of course we...

Yeah, I think that's roughly what I have in mind. I'd add the following as well: * we get a `hir::Node` untyped type, analogous to `SyntaxNode`, so that we can...

Probably makes sense to take a second look at https://docs.microsoft.com/en-us/dotnet/api/microsoft.codeanalysis.semanticmodel?view=roslyn-dotnet-3.9.0, it feels like it has a lot of goodness > IsSpeculativeSemanticModel | Returns true if this is a speculative semantic...