Tweak wording, resolve TODOs

Author: Mark-Simulacrum

posts/2024-09-05-Rust-1.81.0.md

@@ -21,27 +21,23 @@ If you'd like to help us out by testing future releases, you might consider upda
 
 ### `core::error::Error`
 
-1.81 stabilizes the `Error` trait in `core`, allowing usage of the trait in `#![no_std]` libraries.
-
-TODO: What can we actually say about this? It seems like this mostly enables
-things in the ecosystem, but from the langauge/standard library not much has
-actually changed in *this* release?
+1.81 stabilizes the `Error` trait in `core`, allowing usage of the trait in
+`#![no_std]` libraries. This primarily enables the wider Rust ecosystem to
+standardize on the same Error trait, regardless of what environments the
+library targets.
 
 ### New sort implementations
 
 Both the stable and unstable sort implementations in the standard library have
 been updated to new algorithms, improving their runtime performance and
-compilation time. Both of the new sort algorithms try to detect
-incorrect implementations of `Ord` and will panic on such cases if detected.
-
-Users encountering these panics should audit any custom Ord implementations to
-ensure they satisfy the requirements documented in [PartialOrd] and [Ord].
+compilation time.
 
-TODO: Ideally we'd have text somewhere specific to the new detection that helps
-explain how to do this audit or otherwise helps users. This otherwise feels
-pretty opaque to me. We might also want to consider whether some kind of
-transition rather than panic! is best (not sure how else users would find out
-about the problem though). See https://github.com/rust-lang/rust/issues/129561.
+Additionally, both of the new sort algorithms try to detect incorrect
+implementations of `Ord` that prevent them from being able to produce a
+meaningfully sorted result, and will now panic on such cases rather than
+returning effectively randomly arranged data.  Users encountering these panics
+should audit their ordering implementations to ensure they satisfy the
+requirements documented in [PartialOrd] and [Ord].
 
 [PartialOrd]: https://doc.rust-lang.org/nightly/std/cmp/trait.PartialOrd.html
 [Ord]: https://doc.rust-lang.org/nightly/std/cmp/trait.Ord.html
@@ -61,6 +57,12 @@ you can use `#[expect(clippy::undocumented_unsafe_blocks)]` as you transition,
 ensuring that once all unsafe blocks are documented you can opt into denying
 the lint to enforce it.
 
+Clippy also has two lints to enforce the usage of this feature and help with
+migrating existing attributes:
+
+* [`clippy::allow_attributes`](https://rust-lang.github.io/rust-clippy/master/index.html#/allow_attributes) to restrict allow attributes in favor of `#[expect]` or to migrate `#[allow]` attributes to `#[expect]`
+* [`clippy::allow_attributes_without_reason`](https://rust-lang.github.io/rust-clippy/master/index.html#/allow_attributes_without_reason) To require a reason for `#[allow]` attributes
+
 ### Lint reasons
 
 Changing the lint level is often done for some particular reason. For example,
@@ -137,20 +139,31 @@ these types allows us to add more useful methods to these types, such as
 This completes the transition started in [1.71](https://blog.rust-lang.org/2023/07/13/Rust-1.71.0.html#c-unwind-abi),
 which added dedicated `"C-unwind"` (amongst other `-unwind` variants) ABIs for
 when unwinding across the ABI boundary is expected. As of 1.81, the non-unwind
-ABIs (e.g., `"C"`) will now abort on uncaught unwinds, closing the longstanding soundess problem.
+ABIs (e.g., `"C"`) will now abort on uncaught unwinds, closing the longstanding
+soundess problem.
 
 Programs relying on unwinding should transition to using `-unwind` suffixed ABI
 variants.
 
-TODO: Check on status of https://github.com/rust-lang/rust/issues/123231
-
-#### WASI target naming changed
+#### WASI 0.1 target naming changed
 
-Usage of the `wasm32-wasi` target will now issue a compiler warning and request
-users switch to the `wasm32-wasip1` target instead. Both targets are the same,
-`wasm32-wasi` is only being renamed, and this [change to the WASI target](https://blog.rust-lang.org/2024/04/09/updates-to-rusts-wasi-targets.html)
+Usage of the `wasm32-wasi` target (which targets WASI 0.1) will now issue a
+compiler warning and request users switch to the `wasm32-wasip1` target
+instead. Both targets are the same, `wasm32-wasi` is only being renamed, and
+this [change to the WASI target](https://blog.rust-lang.org/2024/04/09/updates-to-rusts-wasi-targets.html)
 is being done to enable removing `wasm32-wasi` in January 2025.
 
+The `wasm32-wasip2` target, which targets WASI 0.2, is now also a tier 2 target.
+See [the announcement post](https://blog.rust-lang.org/2024/09/05/wasip2-tier-2.html) for more details.
+
+#### Fixes CVE-2024-43402
+
+`std::process::Command` now correctly escapes arguments when invoking batch
+files on Windows in the presence of trailing whitespace or periods (which are
+ignored and stripped by Windows).
+
+See more details in the previous [announcement of this change](https://blog.rust-lang.org/2024/09/04/cve-2024-43402.html).
+
 ### Other changes
 
 Check out everything that changed in [Rust](https://github.com/rust-lang/rust/releases/tag/1.81.0), [Cargo](https://github.com/rust-lang/cargo/blob/master/CHANGELOG.md#cargo-181-2024-09-05), and [Clippy](https://github.com/rust-lang/rust-clippy/blob/master/CHANGELOG.md#rust-181).