rust-lang/rust-analyzer

AI Summary: This GitHub issue reports an incorrect type resolution for associated types within qualified paths in a Rust language server. When hovering over `<Foo as A>::Assoc`, the type hint incorrectly shows `()` for type ascription and `fn default<usize>() -> usize` for a path expression, instead of the expected `usize` in both cases. The problem is suspected to be due to generic arguments being dropped during path resolution.

AI Summary: The documentation for `rust-analyzer.check.overrideCommand` provides an example showing a `String` value, but the actual implementation expects a `Vec<String>`. This discrepancy leads to user confusion as the documented example does not work as expected.