stuff

Author: steveklabnik

_posts/2016-12-22-Rust-1.14.md

@@ -16,10 +16,10 @@ website, and check out the [detailed release notes for 1.14.0][notes] on GitHub.
 
 ### 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
-to install Rust from the project directly. Rustup does a bit more than just
-install Rust:
+One of the biggest features in Rust 1.14 isn't actually in the language or
+compiler: the [rustup tool has reached a 1.0 release][rustup], and is now the
+recommended way to install Rust from the project directly. Rustup does a bit
+more than just install Rust:
 
 > rustup installs The Rust Programming Language from the official release
 > channels, enabling you to easily switch between stable, beta, and nightly
@@ -31,14 +31,14 @@ install Rust:
 
 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)
+GitHub](https://github.com/rust-lang-nursery/rustup.rs).
 
 [prev]: https://blog.rust-lang.org/2016/05/13/rustup.html
 
 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
+small taste of how it works, once you have [emscripten] installed, compiling
 some Rust code to WebAssembly is as easy as:
 
 ```bash
@@ -51,7 +51,7 @@ $ node hello.js
 [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
+The community has been doing interesting, experimental work in this area: see
 [Jan-Erik's slides] for the workshop he ran at [Rust Belt Rust] for some
 examples, or check out [Tim's example of the classic TodoMVC project][todomvc].
 This implementation builds off of his [webplatform
@@ -61,6 +61,13 @@ crate](https://crates.io/crates/webplatform), which exposes the DOM to Rust.
 [Rust Belt Rust]: http://www.rust-belt-rust.com/sessions/
 [todomvc]: http://timryan.org/rust-todomvc/
 
+Also of interest is [xargo], which allows for easy cross-compilation of Rust
+to bare-metal targets. If you're writing an operating system in Rust, or
+doing something interesting on a microcontroller, xargo can make your life a
+lot simpler.
+
+[xargo]: https://github.com/japaric/xargo
+
 Speaking of platforms, a large number of platforms have gained additional
 support:
 
@@ -92,8 +99,6 @@ more details.
 
 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
-broadly speaking, compile times should be the same or faster.
 
 [numer of improvements to compile times]: https://github.com/rust-lang/rust/blob/master/RELEASES.md#compile-time-optimizations
 
@@ -148,7 +153,7 @@ match p {
 }
 ```
 
-This was a inconsistency, and so with RFC 1492 stabilized, compiles fine as of
+This was an inconsistency, and so with RFC 1492 stabilized, compiles fine as of
 this release. This applies to more situations than tuples; please see [the
 RFC][RFC 1492] for more details.
 
@@ -161,14 +166,15 @@ fit into particularly nice categories for this release. Here's the highlights:
 
 * [`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]
+* [`Wrapping` impls standard binary and unary operators on references, as well
+  as the `Sum` and `Product` iterators][37356]
 * [Implement `From<Cow<str>> for String` and `From<Cow<[T]>> for
   Vec<T>`][37326]
 * [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]
+* [Don't reuse `HashMap` random seeds][37470]. This helps to mitigate one type
+  of DDoS attack.
 * [The internal memory layout of `HashMap` is more cache-friendly, for
   significant improvements in some operations][36692]
 * [Impl `Add<{str, Cow<str>}>` for `Cow<str>`][36430]
@@ -189,7 +195,7 @@ See the [detailed release notes][notes] for more.
 
 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
+on the MSVC platform. But, mechanically speaking, this means that Cargo will
 now pass along the values printed by `rustc --print cfg` to build scripts.
 
 [RFC 1721]: https://github.com/rust-lang/rfcs/blob/master/text/1721-crt-static.md