Skip to content

Add 1.14 release blog post. #141

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 4 commits into from
Dec 22, 2016

Conversation

steveklabnik
Copy link
Member

r? @rust-lang/core

}
```

This was a inconsistency, and so with RFC 1492 stabilized, compiles fine as of
Copy link
Member

Choose a reason for hiding this comment

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

a inconsistency


### What's in 1.14.0 stable

One of the biggest features in Rust 1.14 isn't actually in Rust 1.14: the
Copy link
Member

Choose a reason for hiding this comment

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

reads weird

Copy link
Member

Choose a reason for hiding this comment

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

Possible change: "One of the biggest features in Rust 1.14 isn't actually in the language itself:"?


As for Cargo, [RFC 1721] has been implemented. The motivation for this feature
is that Cargo can now compile objects for statically linking against the msvcrt
on the MSVC platform. But, meachnically speaking, this means that Cargo will
Copy link
Member

Choose a reason for hiding this comment

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

mechanically

[wasm]: https://users.rust-lang.org/t/compiling-to-the-web-with-rust-and-emscripten/7627
[emscripten]: http://kripken.github.io/emscripten-site/docs/getting_started/downloads.html

The community has been doing intertesting, experimental work in this area: see
Copy link
Contributor

Choose a reason for hiding this comment

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

interesting


### What's in 1.14.0 stable

One of the biggest features in Rust 1.14 isn't actually in Rust 1.14: the
Copy link
Contributor

Choose a reason for hiding this comment

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

perhaps "isn't in the compiler"?

* [`println!()`, with no arguments, prints newline][36825].
Previously, an empty string was required to achieve the same.
* [`Wrapping` impls standard binary and unary operators, as well as
the `Sum` and `Product` iterators][37356]
Copy link
Contributor

Choose a reason for hiding this comment

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

actually the operator impls were already there, this just adds them for references

* [Expand `.zip()` specialization to `.map()` and `.cloned()`][37230]
* [Implement `RefUnwindSafe` for atomic types][37178]
* [Specialize `Vec::extend` to `Vec::extend_from_slice`][37094]
* [Don't reuse `HashMap` random seeds][37470]
Copy link
Contributor

Choose a reason for hiding this comment

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

maybe mention why? (mitigates one type of HashDoS attack)


As for Cargo, [RFC 1721] has been implemented. The motivation for this feature
is that Cargo can now compile objects for statically linking against the msvcrt
on the MSVC platform. But, meachnically speaking, this means that Cargo will
Copy link
Contributor

Choose a reason for hiding this comment

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

mechanically


We had [a previous post about Rustup][prev] back in May. You can learn more
about it there, or by checking it out [on
GitHub](https://github.com/rust-lang-nursery/rustup.rs)
Copy link

Choose a reason for hiding this comment

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

Lacking a period at the end (possibly due to the inline link also containing one)

### What's in 1.14.0 stable

One of the biggest features in Rust 1.14 isn't actually in Rust 1.14: the
[rustup tool has reached a 1.0 release][rustup], and is now the recomended way
Copy link

Choose a reason for hiding this comment

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

recommended

Another exciting feature is [experimental support for WebAssembly][wasm] as a
target, `wasm32-unknown-emscripten`. It is still early days, and there's a lot
of bugs to shake out, so please give it a try and report them! To give you a
small taste of how it works, one you have [emscripten] installed, compiling
Copy link
Member

Choose a reason for hiding this comment

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

once you have


The landing of MIR over the last few releases means that a [number of
improvements to compile times] have landed, with more coming in the future.
Exact numbers are hard, as they depend on what code you're compiling, but
Copy link
Member

Choose a reason for hiding this comment

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

The "exact numbers are hard" seems disingenuous; we have a benchmark suite. If we don't have good overall numbers to report, I'd just drop this sentence.

#### Library stabilizations

There have been a number of additions to the standard library, but they don't
fit into particularly nice categories for this release. Here's the highlights:
Copy link
Member

Choose a reason for hiding this comment

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

It'd be great to provide a sentence description of each of the listed changes.


#### Cargo features

As for Cargo, [RFC 1721] has been implemented. The motivation for this feature
Copy link
Member

Choose a reason for hiding this comment

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

You say "the motivation for this feature" without actually saying what the feature is.

Copy link
Member Author

@steveklabnik steveklabnik Dec 21, 2016

Choose a reason for hiding this comment

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

I was considering "RFC 1721" as the feature, and then explaining the details after, but maybe that's too convoluted. Any suggestions?

[Rust Belt Rust]: http://www.rust-belt-rust.com/sessions/
[todomvc]: http://timryan.org/rust-todomvc/

Speaking of platforms, a large number of platforms have gained additional
Copy link
Contributor

Choose a reason for hiding this comment

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

If we're talking about experimental support for new platforms, how about mentioning xargo?

@steveklabnik
Copy link
Member Author

I thought I had my spellcheck on, sorry about that everyone. Should have everything done except @aturon 's two comments about sentences for library changes, as well as the slight weirdness of phrasing. I might knock those out in the morning.

@brson
Copy link
Contributor

brson commented Dec 21, 2016

I pushed some minor typo fixes.

@steveklabnik
Copy link
Member Author

Okay, this should be good to go 👍

@steveklabnik steveklabnik merged commit bbcf66f into rust-lang:gh-pages Dec 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants