RustDT v0.6.0 Release Notes
Release Date: 2016-05-12 // almost 8 years ago-
- ➕ Added customization of the build command for Build Targets: It's now possible to specify a command other than the default one (the Cargo tool).
- Note however that RustDT still expects the command output (the compiler error messages) to be in the same format as the default tool.
- ➕ Added support for invoking a specific Build Target when a Rust editor is saved. This is called "auto-check", and is intended for build commands that only check for compilation errors, but don't produce artifacts. This has the potential to be faster than a regular build.
- Default is
rustc --lib -- -Zno-trans
. - The goal for the future is to enable invoking this command on-the-fly (as the user types), although for this to be useful in practice it will likely require the compiler to support incremental compilation (or be super fast otherwise).
- Added Building section to documentation.
- Default is
- ➕ Added support for modifying the environment variables of a Build Target's build command. (#72)
- RustDT no longer needs to save the editor before invoking Racer.
- 🆕 New Cargo project can now initialize project using
cargo init
. (#106) - ➕ Added some new code snippets:
enum
,at
andaq
,if
,ifl
,whl
,fn
,fnr
,test
,macro
. (#109)
- 🛠 Fixed "IllegalStateException: The service has been unregistered" on Mars.2 when Eclipse is closed.
- 🛠 Fixed: Running Targets from "crate#tests" failed in OS X due to ".dSYM" dir. (#96)
- 🛠 Fixed: Format tool (
rustfmt
) is invoked when an editor is saved automatically due to code completion. (#101) - 🛠 Fixed: Pressing Tab key does not indent according to Editor indentation preferences. (#99)
- 🛠 Fixed: syntax highlighting for the character literal
'\"'
.
- ➕ Added customization of the build command for Build Targets: It's now possible to specify a command other than the default one (the Cargo tool).