rust-analyzer fails to provide diagnostics after 'rustlings lsp' (Windows 11)

[GersiD]

------problem-statement----

After running rustlings lsp and setting cargo to use all features (for the exercise feature). Rust analyzer still fails to recognize the workspace and populate the exercises subdirectory with diagnostic information.

Please note that I still get Syntax Errors

---------env-info-----------

• Neovim Version: v0.9.0-dev-1147+ge389b1890
• cargo 1.66.0 (d65d197ad 2022-11-15)
• rust-analyzer 1.68.0 (2c8cc343 2023-03-06)

-------what-I-tried--------

1. Run rustligns lsp multiple times after re installing rustlings
2. setting cargo. Features to "exercises"
3. setting cargo.features to "all"
4. updating rust
5. updating rust-analyzer
6. trying to see if VScode gets it
7. manually adding the exercise subdir into the cargo.toml file with

[features]
default = ["exercises"]
exercises = []

None of the above worked :(

[GersiD]

Please tell me what file I should use to test the diagnostics. Currently I am testing traits4.rs (because that's what I made it up to without the diagnostics).

[jnnnnn]

I spent a couple of hours trying to figure this out too (windows 10, the only weird thing about my rust installation is SCCACHE).

I ended up ditching the rust-project.json approach and generating mod files instead.

[GersiD]

@jnnnnn Thank you! this works for rustlings files that are in directories but for things like quiz1,2,3 this solution does not work. I am working out now how to change it so that it works and then I will open a PR with you. Thank you!

Turns out I cannot open a PR with gists. So I forked it and added my changes, if you would like them as well.
https://gist.github.com/GersiD/9f1598cbcf436de56c2c16d88181efa6