intellij-rust VS rust

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

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.

The above Assert<{N % 2 == 1}> requires #![feature(generic_const_exprs)] and the nightly toolchain. See https://github.com/rust-lang/rust/issues/76560 for more info.

Another week, another dive into Rust. This time, we're delving into structs. Structs bear resemblance to interfaces in TypeScript, enabling the grouping of intricate data sets within an object, much like TypeScript/JavaScript. Rust also accommodates functions within these structs, offering a semblance of classes, albeit with distinctions. Let's delve into this topic.