That's probably because you don't have rust-analyzer support enabled – run rustlings lsp once to get that set up. See: https://github.com/rust-lang/rustlings#enabling-rust-analyzer

That's probably because you don't have rust-analyzer support enabled – run rustlings lsp once to get that set up. See: https://github.com/rust-lang/rustlings#enabling-rust-analyzer

No, I had already enabled it. Besides, WebStorm does not use rust-analyzer.

Not sure then, I've heard from people that JetBrains IDEs should just work. Are you using the latest version or are you on main?

Hello, i have exactly same issue.
First i have try to downgrade rust-analyzer to v0.3.1451, try to set root_module to absolute paths (like i could found on #1462), but even with that that still doesn't work...

The only solution i have found is to delete rust-project.json and using the code i have could found here #1421 (comment) for generate mod.rs and now work for most of exercises, but i still have no error on some exercises.

This may be related to the same issue that the people in #1462 were having, @orblazer, by chance, are you using Windows?

@shadows-withal no i use Manjaro with 6.1.26-1-MANJARO kernel version.

Hm, actually not related to that other issue, it seems.

This should be resolved when #1935 is closed.

This should be resolved when #1935 is closed.

@mo8it I just tested the v6 branch (specifically 8c8f30d) and see the same behavior as OP with rust-analyzer in VS Code.

Version data:

% rustc --version
rustc 1.77.2 (25ef9e3d8 2024-04-09)

% rustlings --version
rustlings 6.0.0

% code --version
1.88.1
e170252f762678dec6ca2cc69aba1570769a5d39
arm64

% code --list-extensions --show-versions | grep 'rust-analyzer'
[email protected]

I am sorry for the confusion, but the v6 branch is not really functional yet 😅

As I mentioned in #1919 (comment), I am still working on the code for the next couple of days.