Stream: t-compiler/rust-analyzer

Topic: not getting suggestions on this case ...


Santiago Pastorino (Nov 24 2020 at 14:45, on Zulip):

Hi, rust-analyzer on vim with my configuration is not showing suggesting in a case like ...

Santiago Pastorino (Nov 24 2020 at 14:46, on Zulip):
    let some_char_vec: Vec<char> = some_string.chars().collect();
    some_char_vec.
Santiago Pastorino (Nov 24 2020 at 14:46, on Zulip):

when I write some_char_vec. I don't get anything

Santiago Pastorino (Nov 24 2020 at 14:46, on Zulip):

I'm not sure if this is a limitation, a problem in my configuration or something

Florian Diebold (Nov 24 2020 at 15:04, on Zulip):

that should very much work. Do you get suggestions for other standard library types? Since the type is explicitly specified, this can't really be a type inference problem, so the only reason this could fail is if Vec doesn't resolve

Santiago Pastorino (Nov 24 2020 at 15:05, on Zulip):

I do get suggestions yeah for other standard library types

Santiago Pastorino (Nov 24 2020 at 15:07, on Zulip):

image.png

Santiago Pastorino (Nov 24 2020 at 15:08, on Zulip):

some_char_vec. doesn't return anything

Florian Diebold (Nov 24 2020 at 15:08, on Zulip):

that's really weird. does go to definition work on Vec?

Jeremy Kolb (Nov 24 2020 at 15:37, on Zulip):

I was seeing an issue earlier where this happened and my log was spammed with warning messages from the client saying that it did not expect a command (vscode client side code action stuff)

Jeremy Kolb (Nov 24 2020 at 15:37, on Zulip):

It went away after I restarted r-a

Santiago Pastorino (Nov 24 2020 at 20:14, on Zulip):

to be honest I have no idea

Santiago Pastorino (Nov 24 2020 at 20:14, on Zulip):

I'm switching to LanguageClient-neovim

Last update: Jul 28 2021 at 03:00UTC