rust-analyzer: Compiler errors not being reported (unless they are syntax errors)

Steps to Reproduce

  1. Clone https://github.com/conwayste/conwayste
  2. Checkout commit e07f87b
  3. Open up conwayste/src/client.rs with neovim running LanguageClient-neovim
  4. Go to line 283, and insert the line let () = net_worker; (such that this is the new line 283)
  5. Click Save

Expected Result An error about type mismatches showing the type of net_worker

Actual Result No errors shown.

Version Info rustc 1.45.2 rust-analyzer 0b2b9a5

Log rust-analyzer-bug.log

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 2
  • Comments: 26 (13 by maintainers)

Most upvoted comments

Hi. It appears that rust-analyzer is working normally for me – I can’t reproduce the bug.

Not sure this would be exactly the same root cause. This happens to me as well, but only when I point to anything external in one of the Cargo.toml in the workspace, like:

[dependencies.a2]
 path="../../a2"

It works for some time. And then it stops running cargo check at some moment. Restarting vscode would not help. Re-installing rust-analyzer helps for some minutes of work again.