intellij-rust VS Clippy

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

I couldn't find it in the API guidelines either. From what I understand, the idea is that any trait bounds, which includes generic type parameter bounds and lifetime bound on a type (struct or enum) would be repeated back in the impl block

there is a nice discussion on this issue here: https://github.com/rust-lang/rust-clippy/issues/1689

You should not blindly follow clippy lints. They are sometimes wrong. Another example https://github.com/rust-lang/rust-clippy/issues/9782 .

I often write () = f() to assert that f() is unit. Unfortunately clippy warns on such code ( https://github.com/rust-lang/rust-clippy/issues/9048 ). There are very recent pull requests for this bug, so hopefully this bug will be fixed very soon. But meanwhile I invented this workaround: [()] = [f()] :)

Apart from running clippy on many projects being essential, clippy is also an exceptionally welcoming project, no matter your prior knowledge.

clippy is a great place to get started :) though it isn't exactly new.

clippy is also pretty compiler-adjacent and unlike rust-analyzer uses rustc's internal APIs. Don't let the size of the code base scare you off! It's actually feasible for a newcomer to contribute even such a substantial change as a new lint, and we have issues labeled as "good first issue" that come with mentorship, so you don't need to go it alone.

Yes, you could use it to write a lint. Although you might find it easier to just fork Clippy and add your own lints to their existing framework.

Check out the readme for more information.

They are two of my favorite Rust tools. If you haven’t tried them yet, I highly recommend giving them a try. Clippy can detect various lints in your code and guide you towards writing more idiomatic code. To install Clippy, simply run rustup component add clippy, and to run it within your workspace, execute cargo clippy. For more details, visit Clippy’s GitHub repository.