Rust 1.12 release announcement

_posts/2016-09-29-Rust-1.12.md

@@ -0,0 +1,341 @@
+---
+layout: post
+title: "Announcing Rust 1.12.0"
+author: The Rust Core Team
+---
+
+The Rust team is happy to announce the latest version of Rust, 1.12.0. Rust is
+a systems programming language with the slogan "fast, reliable, productive:
+pick three."
+
+As always, you can [install Rust 1.12.0][install] from the appropriate page on our
+website, and check out the [detailed release notes for 1.12.0][notes] on GitHub.
+1361 patches were landed in this release.
+
+[install]: https://www.rust-lang.org/install.html
+[notes]: https://github.com/rust-lang/rust/blob/stable/RELEASES.md#version-1120-2016-09-29
+
+### What's in 1.12.0 stable
+
+The release of 1.12 might be one of the most significant Rust releases since
+1.0. We have a lot to cover, but if you don't have time for that, here's a
+summary:
+
+The largest user-facing change in 1.12 stable is the new error message format
+emitted by `rustc`. We've [previously talked] about this format and this is the
+first stable release where they are broadly available. These error messages are
+a result of the effort of many hours of [volunteer effort] to design, test, and
+update every one of `rustc`s errors to the new format. We're excited to see
+what you think of them:
+
+![A new borrow-check error](/images/2016-09-Rust-1.12/borrowck-error.png)
+
+The largest internal change in this release is moving to a new compiler backend
+based on the new Rust [MIR]. While this feature does not result in any new
+user-visible features, it paves the way for a number of future compiler
+optimizations, and for some codebases it already results in improvements to
+compile times and reductions in code size.
+
+[previously talked]: https://blog.rust-lang.org/2016/08/10/Shape-of-errors-to-come.html
+[volunteer effort]: https://github.com/rust-lang/rust/issues/35233
+[MIR]: https://blog.rust-lang.org/2016/04/19/MIR.html
+
+#### Overhauled error messages
+
+With 1.12 we're introducing a new error format which helps to surface a lot of
+the internal knowledge about why an error is occurring to you, the developer. It
+does this by focusing on your code and the points of interest in your code that
+are relevant to the error.
+
+For example, in 1.11 if a implementation of a trait didn't match the trait
+declaration, you would see an error like the one below:
+
+![An old mismatched trait
+error](/images/2016-09-Rust-1.12/old-mismatched-trait-error.png)
+
+In the new error format we represent the error by instead showing the points in
+the code that matter the most. Here the relevant line in the trait declaration,
+and the relevant line in the implementation, using labels to describe why they
+don't match:
+
+![A new mismatched trait
+error](/images/2016-09-Rust-1.12/mismatched-trait-error.png)
+
+Initially, this error design was built to aid borrow-checking errors, but we
+found, like the error above, the format can be broadly applied to a wide variety
+of errors. If you would like to learn more about the design, check out the
+[previous blog post on the subject][err].
+
+[err]: https://blog.rust-lang.org/2016/08/10/Shape-of-errors-to-come.html
+
+Finally, you can also get these errors as JSON with a flag. Remember that error
+we showed above, at the start of the post? Here's an example of attempting to
+compile that code while passing the `--error-format=json` flag:
+
+```bash
+$ rustc borrowck-assign-comp.rs --error-format=json
+{"message":"cannot assign to `p.x` because it is borrowed","level":"error","spans":[{"file_name":"borrowck-assign-comp.rs","byte_start":562,"byte_end":563,"line_start":15,"line_end":15,"column_start":14,"column_end":15,"is_primary":false,"text":[{"text":"    let q = &p;","highlight_start":14,"highlight_end":15}],"label":"borrow of `p.x` occurs here","suggested_replacement":null,"expansion":null}],"label":"assignment to borrowed `p.x` occurs here","suggested_replacement":null,"expansion":null}],"children":[],"rendered":null}
+{"message":"aborting due to previous error","code":null,"level":"error","spans":[],"children":[],"rendered":null}
+```
+
+We've actually elided a bit of this for brevity's sake, but you get the idea.
+This output is primarily for tooling; we are continuing to invest in supporting
+IDEs and other useful development tools. This output is a small part of that
+effort.
+
+#### MIR code generation
+
+The new Rust "mid-level IR", usually called "MIR", gives the compiler a simpler
+way to think about Rust code than it's previous way of operating entirely on the
+Rust abstract syntax tree. It makes analysis and optimizations possible that
+have historically been difficult to implement correctly. The first of many
+upcoming changes to the compiler enabled by MIR is a rewrite of the pass that
+generates LLVM IR, what `rustc` calls "translation", and after many months of
+effort the MIR-based backend has proved itself ready for prime-time.
+
+TODO: Improve code complexity: size of old trans vs size of new trans.
+
+While for the most part this new backend is simply laying the groundwork for
+future improvements, this release does include one long-awaited refinement to
+the run-time representation of Rust types that results in both compile-time wins
+and runtime wins: the removal of "drop flags", AKA "non-zeroing drop", as
+specified in [RFC 320].
+
+To maintain the semantics of Rust's `Drop` implementation, we always need to
+check whether a type must be dropped when it goes out of scope. Historically,
+this has been done by adding a special flag to all types that implement `Drop`,
+but this resulted in significant extra memory being used at runtime.
+
+MIR exposes perfect information about the program's control flow, so the
+compiler knows exactly whether types are moved or not. This means that it knows
+statically whether or not the value's destructor needs to be run. In cases where
+a value may or may not be moved at the end of a scope, the compiler now simply
+uses a single bitflag on the stack, which is in turn easier for optimization
+passes in LLVM to reason about. The end result is less work for the compiler and
+less bloat at runtime.
+
+The improvements in compile times of some workloads due to this change alone are
+significant:
+
+|               | 1.11   | 1.12  | compile time |
+|---------------|--------|-------|--------------|
+| inflate-0.1.0 | 10.17s | 4.32s | 2.35x faster |
+| hyper-0.5.0   | 24.03s | 5.23s | 4.58x faster |
+| hellworld     | 0.17s  | 0.14s | 1.20x faster |
+| regex 0.1.30  | 9.63s  | 2.39s | 4.03x faster |
+
+It is worth remembering that not all workloads may see this large of an
+improvement: it depends on a large number of factors.
+
+TODO: Future improvements.
+
+TODO: non-zeroing drop PR https://github.com/rust-lang/rust/pull/33622
+
+Compile times:
+
+|               | 1.11   | 1.12  | % change |
+|---------------|--------|-------|----------|
+| inflate-0.1.0 | 10.17s | 4.32s | -57.5%   |
+| hyper.0.5.0   | 24.03s | 5.23s | -78.2%   |
+| helloworld    | 0.17s  | 0.14s | -16.4%   |
+| regex.0.1.30  | 9.63s  | 2.39s | -75.2%   |
+
+[Memory usage](https://en.wikipedia.org/wiki/Resident_set_size):
+
+|               | 1.11  | 1.12  | % of original size |
+|---------------|-------|-------|--------------------|
+| inflate-0.1.0 | 175MB | 135MB | 77.1%              |
+| hyper.0.5.0   | 321MB | 302MB | 94.1%              |
+| helloworld    | 127MB | 90MB  | 70.9%              |
+| regex.0.1.30  | 230MB | 194MB | 84.3%              |
+
+[RFC 320]: https://github.com/rust-lang/rfcs/blob/master/text/0320-nonzeroing-dynamic-drop.md
+
+#### Library stabilizations
+
+See the [detailed release notes][notes] for more.
+
+#### Cargo features
+
+See the [detailed release notes][notes] for more.
+
+### Contributors to 1.12.0
+
+We had 176 individuals contribute to 1.12.0. Thank you so much!
+
+* Aaron Gallagher
+* abhi
+* Adam Medziński
+* Ahmed Charles
+* Alan Somers
+* Alexander Altman
+* Alexander Merritt
+* Alex Burka
+* Alex Crichton
+* Amanieu d'Antras
+* Andrea Pretto
+* Andre Bogus
+* Andrew
+* Andrew Cann
+* Andrew Paseltiner
+* Andrii Dmytrenko
+* Antti Keränen
+* Aravind Gollakota
+* Ariel Ben-Yehuda
+* Bastien Dejean
+* Ben Boeckel
+* Ben Stern
+* bors
+* Brendan Cully
+* Brett Cannon
+* Brian Anderson
+* Bruno Tavares
+* Cameron Hart
+* Camille Roussel
+* Cengiz Can
+* CensoredUsername
+* cgswords
+* Chiu-Hsiang Hsu
+* Chris Stankus
+* Christian Poveda
+* Christophe Vu-Brugier
+* Clement Miao
+* Corey Farwell
+* CrLF0710
+* crypto-universe
+* Daniel Campbell
+* David
+* [email protected]
+* Diggory Blake
+* Dominik Boehi
+* Doug Goldstein
+* Dridi Boukelmoune
+* Eduard Burtescu
+* Eduard-Mihai Burtescu
+* Evgeny Safronov
+* Federico Ravasio
+* Felix Rath
+* Felix S. Klock II
+* Fran Guijarro
+* Georg Brandl
+* ggomez
+* gnzlbg
+* Guillaume Gomez
+* hank-der-hafenarbeiter
+* Hariharan R
+* Isaac Andrade
+* Ivan Nejgebauer
+* Ivan Ukhov
+* Jack O'Connor
+* Jake Goulding
+* Jakub Hlusička
+* James Miller
+* Jan-Erik Rediger
+* Jared Manning
+* Jared Wyles
+* Jeffrey Seyfried
+* Jethro Beekman
+* Jonas Schievink
+* Jonathan A. Kollasch
+* Jonathan Creekmore
+* Jonathan Giddy
+* Jonathan Turner
+* Jorge Aparicio
+* José manuel Barroso Galindo
+* Josh Stone
+* Jupp Müller
+* Kaivo Anastetiks
+* kc1212
+* Keith Yeung
+* Knight
+* Krzysztof Garczynski
+* Loïc Damien
+* Luke Hinds
+* Luqman Aden
+* m4b
+* Manish Goregaokar
+* Marco A L Barbosa
+* Mark Buer
+* Mark-Simulacrum
+* Martin Pool
+* Masood Malekghassemi
+* Matthew Piziak
+* Matthias Rabault
+* Matt Horn
+* mcarton
+* M Farkas-Dyck
+* Michael Gattozzi
+* Michael Neumann
+* Michael Rosenberg
+* Michael Woerister
+* Mike Hommey
+* Mikhail Modin
+* mitchmindtree
+* mLuby
+* Moritz Ulrich
+* Murarth
+* Nick Cameron
+* Nick Massey
+* Nikhil Shagrithaya
+* Niko Matsakis
+* Novotnik, Petr
+* Oliver Forral
+* Oliver Middleton
+* Oliver Schneider
+* Omer Sheikh
+* Panashe M. Fundira
+* Patrick McCann
+* Paul Woolcock
+* Peter C. Norton
+* Phlogistic Fugu
+* Pietro Albini
+* Rahiel Kasim
+* Rahul Sharma
+* Robert Williamson
+* Roy Brunton
+* Ryan Scheel
+* Ryan Scott
+* saml
+* Sam Payson
+* Samuel Cormier-Iijima
+* Scott A Carr
+* Sean McArthur
+* Sebastian Thiel
+* Seo Sanghyeon
+* Shantanu Raj
+* ShyamSundarB
+* silenuss
+* Simonas Kazlauskas
+* srdja
+* Srinivas Reddy Thatiparthy
+* Stefan Schindler
+* Stephen Lazaro
+* Steve Klabnik
+* Steven Fackler
+* Steven Walter
+* Sylvestre Ledru
+* Tamir Duberstein
+* Terry Sun
+* TheZoq2
+* Thomas Garcia
+* Tim Neumann
+* Timon Van Overveldt
+* Tobias Bucher
+* Tomasz Miąsko
+* trixnz
+* Tshepang Lekhonkhobe
+* ubsan
+* Ulrik Sverdrup
+* Vadim Chugunov
+* Vadim Petrochenkov
+* Vincent Prouillet
+* Vladimir Vukicevic
+* Wang Xuerui
+* Wesley Wiser
+* William Lee
+* Ximin Luo
+* Yojan Shrestha
+* Yossi Konstantinovsky
+* Zack M. Davis
+* Zhen Zhang
+* 吴冉波