It now covers subslice patterns and, in some cases, const generics:Ĭode insight has also received some improvements. For performance reasons, this has been enabled only for types with fewer than a predefined number of aliases (the threshold is set to 10 at the moment).Īnother important improvement concerns type inference.
#INTELLIJ IDEA RUST CODE#
The first change to note here is the introduction of code insight for impl blocks with type aliases.
#INTELLIJ IDEA RUST INSTALL#
The plugin will ask you to install the appropriate version of evcxr_repl, and then you’ll be ready to go. To open the console, call Tools | Rust REPL or search for REPL in the Find Action dialog ( Ctrl+Shift+A on Windows/Linux, Shift⌘A on macOS). It also shows a pane with the list of variables, functions, and structures currently in use. Implemented on top of the evcxr_repl utility, Rust REPL provides syntax highlighting and completion for the code lines you type. This handy tool is a notebook, a calculator, and a Rust interpreter all in one. Simple function calls like fn foo() -> i32 can already be included in the expressions, and we are working on handling more complicated cases.Ī major novelty of this release is the REPL console, an interactive read-eval-print-loop environment for prototyping and testing your code. Moreover, demangled names are now available for Evaluate Expression. The patched version of LLDB is also capable of demangling Rust function names, which allows the plugin to show them in a human-readable format inside the call stack (notice the Frames pane in the screenshot below). Now the debugger can properly show enums and primitive types like i32, which was previously displayed as a C-style int. This patched version of LLDB brings long-awaited improvements in type representation. You can track the progress of this ongoing work in this umbrella ticket.Īs a basis for improving LLDB support, we took the ‘rust-enabled lldb’ patches developed by Tom Tromey, fine-tuned them to suit the recent versions of the debugger, and applied them to CLion’s bundled LLDB. LLDB doesn’t natively support Rust and treats it as C code by default, so the plugin has to do its part to make your debugging experience more convenient. If you are working on macOS or Linux, you have the choice to use LLDB as your Rust debugger. Now, let’s get back to the plugin updates:
#INTELLIJ IDEA RUST DOWNLOAD#
It requires you to download the debugger binaries, which are not bundled.It requires the nativeDebug plugin to work in IntelliJ IDEA Ultimate.It’s available in IntelliJ IDEA Ultimate, AppCode, and RubyMine starting with version 2020.1.It is now possible to debug your Rust code in IDEs other than CLion! Here are a few more details: In this post, we’ll take a look at the updates that IntelliJ Rust has received over the 2020.1 release cycle.īut before we start, we have an exciting announcement that we would like to share.
0 kommentar(er)
