Rust Analyzer completion issues

[TatriX]

rust-analyzer completion is practically unusable.

See also #1269

Describe the bug

Weird completion with rust-analyzer.

To Reproduce

emacs -q -l lsp-start-plain.el

then open src/main.rs, find x. and M-tab.
See attached zip for a test case.
rust-analyzer-tests.zip

Expected behavior
With (setq rustic-lsp-server 'rls)

Which Language Server did you use
rls & rust-analyzer

OS
Arch Linux.
I'm using Emacs from master, and also tried 26.3 just in case.

[kiennq]

If you put the use std::collections::HashMap; outside of function, you can see the proper completions.

[TatriX]

Well, if you use for example diesel, then you are expected to put use statements in your functions. And I do this quite often if I want to test something. It's a legitimate language feature and I expect completion to work in this case.

[flodiebold]

We of course plan to support this, but it is very complicated to implement. You can follow rust-lang/rust-analyzer#1165 for it. TBH, 'practically unusable' and 'I expect' is not the kind of tone that will motivate people to work on this for you though.

[yyoncho]

@TatriX I am closing the PR based on the fact that this is something that has to be fixed on the server and there is nothing address on lsp-mode's side.

[TatriX]

TBH, 'practically unusable' and 'I expect' is not the kind of tone that will motivate people to work on this for you though.

Sorry if that sounded rude, I didn't mean that. It's practically unusable for me right now, not in general. I understood suggestion to move use statement out of the function as "not a bug", so I just wanted to say that it should work in principle as it's what I expect after rls, not that I'm expecting someone to go and fix it for me.