intellij-rust VS rust-tools.nvim

We’ll also consider the cases when IntelliJ IDEA licenses were primarily bought for Rust development with the IntelliJ Rust plugin and which options we can suggest to our users in these cases. Please stay tuned!

https://github.com/intellij-rust/intellij-rust/issues/10867#...

Last time I tried this, the plugin was incapable of actually showing compile errors in the project view and they said their false positive error rate was too high to enable it (https://github.com/intellij-rust/intellij-rust/pull/8373). That was a dealbreaker for me compared to VSCode.

Intellgi Rust is a good option.

Thank you all for the assist. Yep, not just a newbie issue which is surprising. :^) https://github.com/intellij-rust/intellij-rust/issues/10483

Warning about Unused_labels and implementation of MIR Now things are getting interesting

Agreed. Specifically, I've found the intellij rust plugin on top of Clion to be great.

figure out testing, you probably want to structure your app in a way that allows you to run it in testing (Zero to Production has a great approach to that). There are helpers for testing like sqlx::test but CLion Rust plugin doesn't support them yet, it breaks code analysis (afaik the fix is not released yet).

Any closer to getting error highlighting on files working properly (https://github.com/intellij-rust/intellij-rust/pull/8373)? That's a major benefit of rust-analyzer to me.

Could you please clarify whether the problem affects exactly local variables' values or function parameters' values? It is a known bug that the CLion's debugger cannot show function parameters' values on Windows: https://github.com/intellij-rust/intellij-rust/issues/6676. This is a major issue and we are working on it. But if you are facing such problems in any other scenarios, please let us know and share a problematic code snippet if possible

This is not a robust solution to the problem. I haven't worked on a large Rust project, so I do not know if this is valid for all kinds of Rust projects. Maybe there is a better debugging config setups/plugins out there (simrat39/rust-tools.nvim is one from what I have searched for). I plan to keep using this config, till it breaks; and try and fix it when it does.

rust-tools is what I'm currently using, https://github.com/simrat39/rust-tools.nvim

I then took the snippet from, I also changed the path to the correct install path of the above. https://github.com/simrat39/rust-tools.nvim/wiki/Debugging

rust-tools.nvim and crates.nvim should be helpful for you. :)

I'd start with nvim-treesitter, nvim-lspconfig, and use rust-tools.nvim as an accelerant. Any remaining advice I'd have is about Neovim but not about Rust. That advice would also be mostly questions of taste for this-or-that decisions.

Are you using https://github.com/simrat39/rust-tools.nvim/ ?

TIL that if you install Rust via Homebrew (like brew install rust), auto formatting (or more specifically, lsp formatting) doesn't work properly. I used both Rust Analyzer and rust-tools) to setup rust lsp and configured it with tons of options, thinking maybe something will work but somehow, one thing never did - auto formatting. This is the command I use for setting up auto formatting via lsp:

neovim + native lsp with rust-tools.nvim, running nixos so I use flakes for my dev environments

I opened an issue https://github.com/simrat39/rust-tools.nvim/issues/369 after searching for such behavior in existing ones. But I also ask here in case it's a known problem.