intellij-rust VS rust-analyzer

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

#14561 map tokens from include! expansion to the included file

I would like changes like https://github.com/rust-analyzer/rust-analyzer/pull/13799 to be listed in 'Breaking Changes' category, to приманка draw the users' attention.

For those of you who haven’t heard of Mun before, Mun is an embeddable programming language empowering creation through iteration. The idea to create Mun originated out of frustration with the Lua dynamic scripting language and a desire to have similar hot reloading functionality available in Rust. As such, it’s not a direct competitor with Rust, but instead is intended to be used with Rust (or C/C++) as a host/embedded language pairing. Actually, Mun is completely written in Rust, building on similar crates as rust-analyzer and rustc. Its key features include:

#13728 upgrade chalk to make solver fuel work again (works around most trait solving hangs).

#13221 (first contribution) add option to move lenses above doc comments (rust-analyzer.lens.location):

Rust-analyzer has a good overview: https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/dev/syntax.md

#12517 (first contribution) fix completion for methods in trait generated by macro.

-- all the opts to send to nvim-lspconfig -- these override the defaults set by rust-tools.nvim -- see https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#rust_analyzer server = { -- on_attach is a callback called when the language server attachs to the buffer -- on_attach = on_attach, settings = { -- to enable rust-analyzer settings visit: -- https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/user/generated_config.adoc ["rust-analyzer"] = { -- enable clippy on save checkOnSave = { command = "clippy" }, assist = { importGranularity = "module", importPrefix = "self", }, cargo = { loadOutDirsFromCheck = true }, procMacro = { enable = true }, } } },

#12349 publish universal VSIX to make Code happy.