Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Rust 1.27 #257

Merged
merged 7 commits into from
Jun 21, 2018
Merged

Rust 1.27 #257

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
e1a6d33
Rust 1.27
steveklabnik Jun 19, 2018
9c1ae8a
second half
steveklabnik Jun 19, 2018
7f0daae
fix nits
steveklabnik Jun 19, 2018
a08cc2b
@aturon's nits
steveklabnik Jun 21, 2018
9a3361c
allude to 1.27.1
steveklabnik Jun 21, 2018
6cd2d27
typos
steveklabnik Jun 21, 2018
a00e380
tweak wording (thanks @aidanhs)
steveklabnik Jun 21, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 10 additions & 0 deletions _posts/2018-06-21-Rust-1.27.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,16 @@ appropriate page on our website, and check out the [detailed release notes for
[install]: https://www.rust-lang.org/install.html
[notes]: https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-1270-2018-06-21

Additionally, we would like to draw attention to something: just before the
release of 1.27.0, we found [a
bug](https://github.com/rust-lang/rust/pull/51686) in the 'deafault match
Copy link
Contributor

Choose a reason for hiding this comment

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

deafault => default

Copy link
Member

Choose a reason for hiding this comment

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

default

bindings' feature introduced in 1.26.0 that can possibly introduce unsoundess.
Copy link
Member

Choose a reason for hiding this comment

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

*unsoundness

Since it was discovered very late in the release process, and has been present
since 1.26.0, we decided that it was not worth deviating from our release train
model. We expect to put out a 1.27.1 with that fix applied soon, and if there's
demand, possibly a 1.26.3 as well. More information about the specifics here
will come in that release announcement.

## What's in 1.27.0 stable

This release has two big language features that people have been waiting for.
Expand Down