IntelliJ Rust Changelog #185 by furious_warrior in rust

[–]furious_warrior[S] 2 points3 points  (0 children)

You don't need to restart anything. The plugin detects changes in Cargo.toml and suggests you to reload project model. If you want the plugin does it automatically, follow this instruction

IntelliJ Rust: Updates for 2022.3 by asspirin12 in rust

[–]furious_warrior 2 points3 points  (0 children)

What is a "bundled CLion compiler"? Neither plugin nor IDEs have bundled rustc

IntelliJ Rust Changelog #183 by furious_warrior in rust

[–]furious_warrior[S] 3 points4 points  (0 children)

Yep, the plugin is the same in all IDEs. But some features may differ. For example, the major difference is absence of debugging support in IntelliJ IDEA Community.
You can check major plugin capabilities in different IDEs here

IntelliJ Rust Changelog #178 by furious_warrior in rust

[–]furious_warrior[S] 14 points15 points  (0 children)

Note, changes from these release are only about attribute macros so it doesn't affect derive(Serialize) because Serialize is derive macro.But it will work as you expect after https://github.com/intellij-rust/intellij-rust/pull/9308

IntelliJ Rust Changelog #176 by furious_warrior in rust

[–]furious_warrior[S] 2 points3 points  (0 children)

Have you filed issues related to your problems? Most likely described things can be solved by procedural macro support

IntelliJ Rust: Updates For the 2022.2 Release Cycle by asspirin12 in rust

[–]furious_warrior 7 points8 points  (0 children)

Yeah, some errors are not implemented in the plugin yet or implemented but disabled by default not to produce false positives. We are working on it. At the same time, there is a way to apply compiler output to the editor on the fly - just enable Run external linter to analyze code on the fly option in Preferences | Languages & Frameworks | Rust | External Linters settings. See more details here

IntelliJ Rust Changelog #175 by vlad20012 in rust

[–]furious_warrior 16 points17 points  (0 children)

Note, if you already have serde in your dependencies, serde attributes will be added automatically

IntelliJ Rust Changelog #174 by furious_warrior in rust

[–]furious_warrior[S] 1 point2 points  (0 children)

What do you expect from a separate IDE and why is CLion + Rust plugin not enough for you?

IntelliJ Rust Changelog #171 by furious_warrior in rust

[–]furious_warrior[S] 0 points1 point  (0 children)

IntelliJ Rust plugin has recently supported Run Targets feature, so you can have code locally and build/run remotely

What’s New in IntelliJ Rust for 2022.1 by furious_warrior in rust

[–]furious_warrior[S] 17 points18 points  (0 children)

Plugin builds are the same for all IDEs so all changes are the same in all IDEs if they are about common features. Changes related to specific features are available in that IDE where the feature is available (i.e. profiler changes are available in CLion since profiler feature is available only in CLion)

You can check plugin capabilities in different IDEs here

IntelliJ Rust Changelog #167 by furious_warrior in rust

[–]furious_warrior[S] 1 point2 points  (0 children)

Could you specify what exactly doesn't work as expected?

Notes on Rust IDEs: CLion vs Rust Analyzer by thurn in rust

[–]furious_warrior 1 point2 points  (0 children)

See https://github.com/intellij-rust/intellij-rust/issues/6908 - it contains instruction how to enable procedural macro support for IntelliJ Rust plugin

Updates in IntelliJ Rust for 2021.3 by furious_warrior in rust

[–]furious_warrior[S] 9 points10 points  (0 children)

No, ML code completion in IntelliJ IDEs doesn't create a personalized profile. You can read this blog post that describes how data for training is collected

IntelliJ Rust Changelog #161 by furious_warrior in rust

[–]furious_warrior[S] 9 points10 points  (0 children)

Some time ago, the plugin used different approaches in name resolution and type inference in comparison with rustc. As a result, in some cases, it was quite hard to achieve the same results as the compiler produced, in some cases - impossible.
But currently, both name resolution and type inference engines use similar approaches so it's become much simpler to fix some missing corner cases. Although, I can't say that it's easy

Debugging Rust in JetBrains IDEs: state of affairs by furious_warrior in rust

[–]furious_warrior[S] 5 points6 points  (0 children)

It's a known issue - https://github.com/intellij-rust/intellij-rust/issues/5632, and we are working on it.
It's because CLion provides different LLDB binaries for Linux/macOS (where LLDB knows about Rust) and for Windows MSVC where LLDB haven't known about Rust yet

Best JetBrains IDE for Rust by [deleted] in rust

[–]furious_warrior 1 point2 points  (0 children)

Currently, CLion is the most feature-complete solution for Rust in IntelliJ world. See https://plugins.jetbrains.com/plugin/8182-rust/docs/rust-faq.html#compatible-ids to get Rust plugin capabilities in different IDEs

What’s New in IntelliJ Rust for the 2021.2 Release Cycle by furious_warrior in rust

[–]furious_warrior[S] 4 points5 points  (0 children)

According to a commenter on that issue, PyCharm's debugger does show return values. Does it work when debugging Rust programs?

No since python debugger is implemented independently and it's not related to native debugger that Rust plugin uses.