JetBrains updates RustRover to 2025.3.4 with editing and configuration improvements

RustRover 2025.3.4 ships a compact set of developer-facing edits and project-configuration fixes that affect day-to-day Rust editing: a new intention action to flip between for_each and for loops, new module visibility options in the New Rust File dialog, improved Cargo.toml validation for autolib, and fixes for bytemuck::Zeroable references. These changes target quick refactors and Cargo validation gaps that surface during routine coding and crate setup.

Those point improvements arrive on top of the larger RustRover 2025.3 feature train. JetBrains says, "RustRover 2025.3 introduces a new LLDB expression evaluator, AI‑powered trait implementation and idea comparison, a floating popup action menu for faster editing, and custom Cargo profile support in the drop-down menu. This release also includes a wide range of fixes and performance improvements for a smoother and faster workflow." The 2025.3 baseline adds debugger expression evaluation and Cargo profile controls that 2025.3.4 builds against.

On the editing surface, the 2025.3.4 intention lets you convert closures used by Iterator::for_each into explicit for loops and back via the IDE intention menu - the release notes phrase this as a "new intention action to flip between `for_each` and `for` loops." The New Rust File dialog now exposes "new module visibility options in the New Rust File dialog" to reduce manual edits after file creation. Project configuration checks gain "improved Cargo.toml validation for autolib," and a targeted fix addresses "fixes for bytemuck::Zeroable references" to prevent spurious analysis or editing errors involving bytemuck types.

The UX and AI features introduced in 2025.3 remain relevant to users upgrading to 2025.3.4. JetBrains highlights a "New floating popup with AI actions" and instructs: "Select any piece of code to instantly access context-aware actions, including some of the new AI features. This addition improves the visibility of the available actions for any code selection and helps you stay focused on what’s important." Terminal integration also improves completion with "completion that suggests commands, option names, and path parameters."

Access and licensing remain the same on JetBrains' product page, which lists RustRover as "Free for non-commercial use" and notes a "Free 30-day trial available" for users evaluating the IDE or its paid tiers.

Community reaction since the RustRover launch has mixed notes and practical advice. A Hacker News thread titled "JetBrains releases RustRover IDE for Rust development (infoworld.com) | 172 points by thunderbong on May 25, 2024" collected comments noting the "free for non-commercial use" license and some controversy over removal of JavaScript/TypeScript support - a community snippet reads in part, "Notably, there's a 'free for non-commercial use' license... There's also controversy because JetBrains removed JavaScript/TypeScript support from RustRover right before this release, admittedly because they want to keep these features gated behind a paid subscription in IntelliJ. That wouldn't normally be an issue, except the IntelliJ Rust plugin is deprecated and doesn't have the support that RustRover does; so there's currently no [...]" (snippet truncated). Users on that thread also posted firsthand takes: armchairhacker wrote, "I can attest to that. Am using Ultimate and everything works and gets regular updates. That includes Rust and web development. I have been a happy paying customer for 10+ years." hwbunny advised, "You can always beta test their cutting edge releases and use those versions for free for 1 month. Don't whine about Jetbrains, they give you several options if you don't have the money to use their products."

JetBrains maintains a visible release cadence in its blog archive with posts such as "RustRover 2025.2 Is Now Available" and "RustRover 2025.1 Is Now Available" by Tatiana Parshutkina, and earlier IntelliJ Rust updates by Marina Kalashina and Sergey Kozlovskiy listed on the product pages.

For verification before broader coverage, obtain JetBrains' official changelog entry for RustRover 2025.3.4, request JetBrains comment on the bytemuck::Zeroable fix and the exact list of module visibility options, and confirm the precise behavior and UI wording for the new for_each ↔ for intention and the Cargo.toml autolib validation changes.

Tried the new for_each ↔ for intention yet? Tell us the exact menu text you saw and the date you tested it.