IntelliJ Rust • Hacker News Board

Re: IntelliJ Rust

#61

Post by anuraaga » Thu, Jul 13, 2023, 11:00 AM UTC

19h wrote: post #39

thurn wrote: post #27

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. It doesn't look like that's changed?

Using it everyday and I can’t confirm this at all. Worst case you can enable clippy to run in the background.

I suspect they did eventually enable it by default to match expectations. I generally see a rate of actually showing compilation errors of around 70%? Perhaps higher, it's not the 100% of other languages like Java/Go, and anecdotally I feel a higher rate with JS.

Re: IntelliJ Rust

#62

Post by itsTyrion » Fri, Jul 14, 2023, 12:04 PM UTC

eulgro wrote: post #55

The plugin is better than nothing but not really up to par with Jetbrains standards yet. - More than half of compile time errors are not shown in the IDEs. - Breaks when using some macros. For example wheb using gtk-rs each file defining a custom widget constantly show 2 errors that aren't there. Autocompletion fails for a lot of macros, even simple ones with macro_rules!. - The debugger works but there are no type r…

Set it to Clippy and real-time lint instead of cargo check

Re: IntelliJ Rust

#63

Post by eulgro » Sun, Jul 16, 2023, 2:51 AM UTC

itsTyrion wrote: post #62

eulgro wrote: post #55

The plugin is better than nothing but not really up to par with Jetbrains standards yet. - More than half of compile time errors are not shown in the IDEs. - Breaks when using some macros. For example wheb using gtk-rs each file defining a custom widget constantly show 2 errors that aren't there. Autocompletion fails for a lot of macros, even simple ones with macro_rules!. - The debugger works but there are no type r…

Set it to Clippy and real-time lint instead of cargo check

Ah thanks it works better. The false positive errors are still there and it takes like 15 sec before errors show up though. I guess it's better still.