Florian Diebold

Probably https://github.com/rust-lang/chalk/issues/727 like https://github.com/rust-lang/rust-analyzer/issues/14949 and https://github.com/rust-lang/rust-analyzer/issues/14933.

@davidbarsky That's the same as #10653 which I'm not so sure is the same as this issue, since there are no trait bounds on type parameters in the original example...

Probably another instance of https://github.com/rust-lang/chalk/issues/727 or https://github.com/rust-lang/chalk/issues/750; it will probably get fixed with the new trait solver (and not before).

These lints are all "WeakWarning" level, which VSCode shows in a very inconspicuous way, just some dots to give a hint you can do something there; the `inactive-code` is also...

Sorry, we apparently call "WeakWarning" what's called "Hint" on the LSP level. It's not a non-standard extension.

I don't know. I think these hints are more intended as "there's a useful thing to do here", not necessarily that there's something wrong. And you might not be using...

Why would we want to "minimize the difference in experience between those who use [rust-analyzer] and those who don't"? You can always turn off any of these diagnostics using the...

@zhiqiangxu probably not the same issue.

It seems to me this broke during some refactoring. It was originally reported as #250; then https://github.com/jwiegley/use-package/commit/9ce42841c4cef69150ae89261ed8a6e881fae85c supposedly fixed it, and the part where hooks are run when e.g. `:config...

Salsa the library is an implementation of the Salsa algorithm. Also, the red-green algorithm (which is another name for the same thing) is used in rustc, it's just not using...