Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • 63
    The problem for me was that my rust-analyzer vscode plugin was indexing. Once it finished, running cargo run worked fine. Commented Feb 11, 2022 at 22:17
  • 14
    I've the same problem on Linux when using Rustler to use Rust codes in Elixir. The problem resolved by removing ~/.cargo/.package-cache as mentioned it this issue github.com/rust-lang/cargo/issues/9742. Commented Apr 3, 2022 at 2:18
  • My problem was that I installed both Rust and rust-analyzer on VS Code at the same time. The problem was fixed after I removed either of the extensions. Hope this helps! Commented Jun 25, 2022 at 12:12
  • 1
    VSCode was my hang up as @oriont stated. I just needed to wait for the rust-analyzer to finish whatever it was doing. Commented Nov 4, 2022 at 17:08
  • 1
    I'm sure this will only apply to a small percentage of users, but for me, restarting Visual Studio Code fixed the problem Commented Nov 23, 2022 at 23:43