liv
liv
Weird, but this sounds like a `rust-analyzer` (the LSP implementation) issue rather than on our end. All that running `rustlings lsp` does is generate a file that `rust-analyzer` can read...
If the condition doesn't go into the `if` block, it'll return `()` (the unit type) at the end of a function by default. The easiest way to fix this would...
Huh yeah, I can't reproduce this. Could you provide a snapshot of your repo that I can clone to check?
What I can tell from your `tests3` is that you'd need to use `assert_eq!` instead of `assert!` for your solution. Fixing that makes `verify`/`watch` pass all the way to `iterators2`....
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
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`?
This may be related to the same issue that the people in #1462 were having, @orblazer, by chance, are you using Windows?
Hm, actually not related to that other issue, it seems.
It's not an issue on our end, the `rust-project.json` specification hasn't changed afaik (if it did, it'd break on non-Windows platforms as well). I'm not sure what the rust-analyzer developers'...
Seems like https://github.com/rust-lang/rust-analyzer/issues/14663 has been posted, backlinking it here to help those in that issue.