You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That means that you use a severely outdated version of the VS Code extension. Have you installed the analyzer from the master branch using cargo install-code command?
Note that we could have renamed the plugin itself (probably? I don't remember), so it might be a good idea to check vscode extensions list for a stale one.
No, there's only one plugin. But it's possible that forgot cargo install-lsp the first time, so an outdated version was used. Thanks anyway for the help ;)
Activity
matklad commentedon Feb 13, 2019
That probably means rust analyzer is not actually working. Does the "Rust Analyzer: Status" command works?
Aloso commentedon Feb 13, 2019
No, it doesn't. Can I fix it?
matklad commentedon Feb 13, 2019
Probably, but we need to figure out what's wrong in the first place :)
Is there "rust-analyzer" section in the "Output" tab of the vs code panel?
Aloso commentedon Feb 13, 2019
The tab is empty.
Aloso commentedon Feb 13, 2019
I'm confused, because when I hover over a struct or trait name, the definition is shown. Doesn't this mean that ra is working?
Aloso commentedon Feb 13, 2019
I just re-installed it. Now the output says:
Aloso commentedon Feb 13, 2019
When I press Enter, this is printed to the output:
matklad commentedon Feb 13, 2019
That means that you use a severely outdated version of the VS Code extension. Have you installed the analyzer from the master branch using
cargo install-codecommand?Aloso commentedon Feb 13, 2019
Yes, I did. However, I just did a
git pull, thencargo install-lspandcargo install-code, and now Enter works.matklad commentedon Feb 13, 2019
Note that we could have renamed the plugin itself (probably? I don't remember), so it might be a good idea to check vscode extensions list for a stale one.
Aloso commentedon Feb 13, 2019
No, there's only one plugin. But it's possible that forgot
cargo install-lspthe first time, so an outdated version was used. Thanks anyway for the help ;)DJMcNab commentedon Feb 13, 2019
We have renamed the plugin I think.