|Rust 2018 Released To Improve Developer Productivity|
|Written by Mike James|
|Friday, 14 December 2018|
Rust 2018 has now been released. This is the first major release since Rust 1.0 in 2015, and alongside new language features, it includes IDE support, updated libraries, new documentation, domain working groups, and a new website.
Rust has been designed to be a safe, fast and concurrent language without having a garbage collector. It is constructed so that problems are detected at compile time so that it can be used safely for systems programming. Rust was originally sponsored by Mozilla, and is intended for use in situations including embedding in other languages, writing programs with specific space and time requirements, and writing low-level code, like device drivers and operating systems.
The new version of Rust will still support Rust 2015 compatible code, and in fact will default to that. There are breaking changes in this release, but these will be the only breaking changes for the next three years of development, and you will still be able to work around the breaking changes.
One of the main changes to the actual language in the new version is support for
The majority of changes, though, are to things like tooling, with the development team focusing on specific ways Rust is used and trying to make it more productive for those specific cases.
Alongside the core tools familiar from earlier versions - Cargo, Rustdoc, and Rustup, new tools have been added: Clippy, Rustfmt, and IDE support.
Rustfmt is a tool for formatting Rust code. Automatically formatting your code lets you save time and arguments by using the official Rust style. This release includes Rustfmt 1.0.
The work on IDE support is, according to the developers, one of the most requested tooling features for Rust. However, IDE support remains a work in progress, though you can work on Rust code in Visual Studio Code, IntelliJ, Atom, Eclipse, and Sublime Text 3. The developers acknowledge that code completion is not up to scratch in the RLS-based editors, but say that if you mainly want support for types, documentation, and 'go to def', etc. then you should be happy.
or email your comment to: firstname.lastname@example.org