more fixes

Author: steveklabnik

_posts/2018-03-01-Rust-1.24.1.md

@@ -23,12 +23,12 @@ appropriate page on our website, and check out the [detailed release notes for
 
 ## What's in 1.24.1 stable
 
-As you know, we tend not to release point releases. In this case, Several minor
-regressions were found in 1.24.0 which collectively merited a release.
+Several minor regressions were found in 1.24.0 which collectively merited a
+release.
 
-A quick summary of the changes: there are four.
+A quick summary of the changes:
 
-* Do not abort when unwinding through FFI (this reverts behavior from 1.24.0)
+* Do not abort when unwinding through FFI (this reverts behavior added in 1.24.0)
 * Emit UTF-16 files for linker arguments on Windows
 * Make the error index generator work again
 * Cargo will warn on Windows 7 if an update is needed.
@@ -41,9 +41,11 @@ With that, let's dig into the details!
 
 ### Do not abort when unwinding through FFI
 
-TL;DR: the behavior in 1.24.0 broke the `rlua` crate, and is being reverted. If
-you have since changed your code to take advantage of the behavior in 1.24.0,
-you'll need to revert it for now.
+TL;DR: the new behavior in 1.24.0 broke the `rlua` crate, and is being
+reverted. If you have since changed your code to take advantage of the behavior
+in 1.24.0, you'll need to revert it for now.  While we still plan to introduce
+this behavior eventually, we will be rolling it out more slowly and with a new
+implementation strategy.
 
 Quoting [the 1.24 annoucement](https://blog.rust-lang.org/2018/02/15/Rust-1.24.html):
 
@@ -64,16 +66,9 @@ extern "C" fn panic_in_ffi() {
 >
 > In Rust 1.24, this code will now abort instead of producing undefined behavior.
 
-As implemented, this functionality broke some users, notably, integration with
-the Lua language. We have reverted this behavior, and 1.24.1 will reintroduce
-the undefined behavior. Fundamentally, the aborting behavior we originally
-rolled out is a soundness fix, and we still plan on reintroducing it, but are
-going to be rolling it out a bit more slowly, and with a different
-implementation.
-
-It started with [a bug filed against the `rlua`
-crate](https://github.com/chucklefish/rlua/issues/71). `rlua` is a package
-that provides high level bindings between Rust and the [Lua programming
+As mentioned above, this caused breakage. It started with [a bug filed against
+the `rlua` crate](https://github.com/chucklefish/rlua/issues/71). `rlua` is a
+package that provides high level bindings between Rust and the [Lua programming
 language](https://www.lua.org/).
 
 > Side note: `rlua` is maintained by [Chucklefish](https://chucklefish.org/),
@@ -187,8 +182,8 @@ we may backport, otherwise, this functionality will be back in 1.26.
 
 ### Emit UTF-16 files for linker arguments on Windows
 
-TL;DR: `rustc` stopped working for some Windows users. If it's been working for you,
-you were not affected by this bug.
+TL;DR: `rustc` stopped working for some Windows users in edge-case situations.
+If it's been working for you, you were not affected by this bug.
 
 In constrast with the previous bug, which is very complex and tough to understand,
 this bug's impact is simple: if you have non-ASCII paths in the directory where