[nvim] rust-analyzer fails to provide autocomplete for new crates

[smadman]

Hello, today I installed nvim with rust-analyzer everything works smoothly. The problem arises when I add a new crate via the cargo add command or the cargo.toml file.

Problem description
After adding the crate I see that rust analyzer is doing something because it deactivates error messages and suggestions and a while later I get updated suggestions. But when I try for example to import the new crate by typing use crate_name:: nothing comes. This is strange because rust analyzer says Consider importing this crate.
I noticed that everything started to work as expected only after I manually typed :LspRestart to restart the server.

What I tried

• I tried different configurations for nvim (including the ones suggested in the rust analyzer website)
• Using rust analyzer from mason
• Using rust analyzer from rustup

Is someone experimenting the same behavior? Any help is accepted.

[nerditation]

for vscode, there's "rust-analyzer reload workspace" command, the nvim equivalence should be :CargoReload. if you save Cargo.toml in vscode, this command will automatically run, I'm not a vim user, so I don't know how to configure neovim to monitor file change and trigger a command.

[vague]

Can't reproduce in my nvim.

I've made my own configs from scratch for two years, use them (but not using mason) in daily Rust programming, and come across minor problems from time to time which might be similar to yours.
If the problem only occasionally appears and LspRestart works, then it's not a big deal at least for me.

But here are some suggestions:

• you can try https://helix-editor.com/ which works out of the box and brings the core basic & lsp functionalities from neovim to check if the problem still exists
• starting your own config is hard: I think the best way to use neovim now is https://www.lazyvim.org/ ^[1] or GitHub - nvim-lua/kickstart.nvim: A launch point for your personal nvim configuration (based on lazy.nvim), because
  • you don't actually repeat the common lsp configs and a lot of stuff that's expected to work normally
  • it won't increase your startup time too much as your plugins are increasing

---

1. I now turn to lazy.nvim ↩︎

[smadman]

Ok so I have tried the :CargoReload command and this fix the problem without needing to restart the whole lsp. Maybe there something wrong in my config. If i found something i will update here.
Thanks to everyone for the help

[smadman]

I have tried with a clean config using kickstart.vim, installed rust-analyzer with mason and there is the same problem. @vague can i ask what version of rust analyzer are you using? Mine is:

rust-analyzer 0.3.1641-standalone

[vague]

Same version.

@smadman

The problem arises when I add a new crate via the cargo add command or the cargo.toml file.

Now I can reproduce the problem via the former in neovim and vscode: can't get autocompletion working on the added crate after cargo add it.

• rust-analyzer-completion-nvim on Vimeo
• rust-analyzer-completion_vscode on Vimeo

But the autocompletion works in neovim and vscode after editing Cargo.toml directly.

• rust-analyzer-completion-nvim-works on Vimeo
• rust-analyzer-completion-vscode-works on Vimeo

I guess it's a bug around rust-analyzer, and I submited one: Autocompletion for newly added crate doesn't work after `cargo add` it, but works after editing Cargo.toml directly · Issue #15554 · rust-lang/rust-analyzer · GitHub

[smadman]

Thanks, hope it gets fixed. For the moment I'll mark your post as solution.