Sorry if this isn't really Rust-centered, but I didn't know where to ask.
Is it only me or after the last update RustRover stopped working correctly? It gives me nonsensical syntax errors, like in almost every line (Pretty much all of the screen is red from errors lol). Obviously they're not real errors, because cargo check and cargo clippy both work normally.
1 Like
As an aside, the 2025.2 series feels like it has introduced a lot of small glitches, which IME is unusual. I hope it's not due to the use of LLMs to write code, or due to the focus on AI features that leaves the rest of the application poorly maintained…
1 Like
I noticed (and reported) a few. A few others were fixed, to be fair. But I've experienced new bugs in their products on a regular basis for years, many of them left unfixed for a very long time; JetBrains seems to prioritize new features like AI assistants and a redundant UI mimicking VSCode, of all things... A common trait of companies aggressively trying to acquire more customers, I suppose.
Despite that, there's still no comparable IDE, but I do hope they're not using LLMs for the development, or it may not last much longer.
This particular bug seems to be limited to recent nightly versions of Rust, though, so I'd say it comes along with the risk of using them. I haven't met that issue so far, even when working with procedural macros.
1 Like
For me it's not just a few bugs, the whole rustrover code analyzer stopped working and gives me syntax errors in almost every line like in function returns and match statements.
Well, it's one bug, but a very annoying one.
Have you seen this comment? It seems to solve the problem if you update nightly.
Otherwise, I doubt reverting to an older RustRover version would help with that one, but have you tried with the stable version of the Rust toolchain? Unless you are forced to use nightly in the IDE, of course.
If that's still not solving the issue, it may be possible to disable just a particular inspection or the intention related to procedural macros.
I'm using the stable one actually, so IDK. Anyway I'll try to update both it and the nightly version and see if that works.
Also, I don't know why we started talking about procedural macros but I'm bot even using them. That's why I'm a bit comfused of that issue in the jetbrains site, because rustrover thinks my code is full of syntax errors and I'm not using any macro at all.
But you marked it as a solution (Wrong proc macro expansion since nightly-2025-11-25), so we all assumed it was the origin of your problem...
Have you reported the bug in Youtrack as a separate issue, then? Could you share the link?
You didn't give any information on your system, either: is it Windows or Linux? And more importantly, which version exactly of RustRover are you using? Did it happen after an update, and if not, did something specific triggered it?
It would also help to know what errors you see: does it look like it's coming from the analyzer with a compiler-like message if you do Ctrl+F1 (Error Description), or does it come from an inspection (and if so, which—try Alt+Enter)? Some of those inspections are quite aggressive, some are even tagged as experimental. You could try to disable all the Rust inspections, for ex.
Do you have the same problem in all your projects, even a small one like what RustRover generates with "New project"? Can you give a minimal code so we can try to reproduce the problem and see if it's related to RustRover alone or to a particular environment?
Other things I'd recommend trying:
- I'm sure you tried already, but just in case, it's worth doing the
Invalidate Cachesand enable "Clear file system cache..." - Backup your settings, then reset them entirely.
- Test on a fresh installation, if you have access to another PC. Sometimes, the JetBrains IDEs get in a messed state; it might help to clean the local cache entirely if you know where it's located.
- Try another version, like the 2025.3 EAP10.
I marked that as a solution because it linked the correct site where to look, or at least i thought. I mean I thougut that response meant this was not the correct place to ask this question, and linked the correct one.
I'm using macOS actually.
It did happen after the lasr update (I'm usong Rustrover's last version)
From the analyzer.
I've also tried to create a new project and it gives the same problem (the one where I had it originally is also a small project, I started it a few days ago)
Sorry, but I really can't help you with so little information.
I assume it means you haven't reported the problem. You're better off doing just that; the JetBrains support will ask you what they need if you don't give enough info. Perhaps they're already aware of the problem.
I will probably report the problem, thanks.
Update: it looks like when it start giving syntax errors I can just cut-paste the code and it stops giving them, so this is half resolved (?).