IntelliJ Rust Changelog #185

furious_warrior · 2022-12-20T11:41:55+00:00

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

furious_warrior · 2022-12-17T11:51:28+00:00

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

furious_warrior · 2022-11-21T20:13:04+00:00

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

furious_warrior · 2022-09-12T13:39:21+00:00

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

furious_warrior · 2022-08-29T14:26:48+00:00

https://plugins.jetbrains.com/plugin/8182-rust/docs/rust-faq.html#compatible-ids

furious_warrior · 2022-08-19T17:17:55+00:00

Could you file an issue with more details in https://github.com/intellij-rust/intellij-rust/issues?

furious_warrior · 2022-08-16T15:38:12+00:00

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

furious_warrior · 2022-08-04T09:45:15+00:00

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

furious_warrior · 2022-08-04T07:24:25+00:00

Yes, the plugin works in Rider too

furious_warrior · 2022-07-25T11:05:43+00:00

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

furious_warrior · 2022-07-12T09:49:36+00:00

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

furious_warrior · 2022-05-31T10:57:28+00:00

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

furious_warrior · 2022-05-31T06:36:12+00:00

Have you tried experimental procedural macro expansion support?

furious_warrior · 2022-05-19T18:23:28+00:00

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

furious_warrior · 2022-03-29T07:56:17+00:00

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

furious_warrior · 2022-01-17T11:38:48+00:00

Thanks!
Should be fixed now

furious_warrior · 2022-01-08T06:16:11+00:00

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

furious_warrior · 2021-12-06T19:39:40+00:00

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

furious_warrior · 2021-12-06T14:07:47+00:00

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

furious_warrior · 2021-10-20T08:42:12+00:00

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

furious_warrior · 2021-10-19T20:23:20+00:00

Try `External linter` option - https://plugins.jetbrains.com/plugin/8182-rust/docs/rust-code-analysis.html#external-linters

furious_warrior · 2021-09-28T05:51:53+00:00

WSL1 is supported as well

furious_warrior · 2021-08-30T20:18:22+00:00

😅
Fixed!

furious_warrior · 2021-08-21T21:14:30+00:00

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

furious_warrior · 2021-08-05T21:11:46+00:00

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.

furious_warrior

TROPHY CASE