Skip to content

Rust 1.12 release announcement #126

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 20 commits into from
Sep 29, 2016
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
re-work intro
  • Loading branch information
steveklabnik committed Sep 27, 2016
commit aebe579efd6c9730e94399965089768d0a09bdcf
20 changes: 11 additions & 9 deletions _posts/2016-09-29-Rust-1.12.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,20 +16,22 @@ website, and check out the [detailed release notes for 1.12.0][notes] on GitHub.

### What's in 1.12.0 stable

Oh my god! So much stuff!
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:

With 1.12 stable, one of the first visible changes you will notice is the new
error message format emitted by `rustc`. We've [previously talked] about this
format and this is the first 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:
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 mismatched trait
error](/images/2016-09-Rust-1.12/mismatched-trait-error.png)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to use the same trait error in both this section and the expanded section below? Might read better to have pictures of a different kind of error here.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I agree


The other major 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
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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Repeating the word "feature" sounds weird, I would change the first occurrence to "change".

optimizations, and for some codebases it already results in improvements to
compile times and reductions in code size.
Expand Down