Update the min_exhaustive_patterns section

Co-authored-by: Kevin Reid <[email protected]>

Author: cuviper

posts/2024-10-17-Rust-1.82.0.md

@@ -57,33 +57,33 @@ The Rust target `aarch64-apple-darwin` for macOS on ARM64 (M1-family or later Ap
 
 [The targets](https://doc.rust-lang.org/nightly/rustc/platform-support/apple-ios-macabi.html) are now tier 2, and can be downloaded with `rustup target add aarch64-apple-ios-macabi x86_64-apple-ios-macabi`, so now is an excellent time to update your CI pipeline to test that your code also runs in iOS-like environments.
 
-### Minimal exhaustive patterns
+### Omitting empty types in pattern matching
 
-Empty patterns can now be omitted in common cases:
+Patterns which match empty (a.k.a. uninhabited) types by value can now be omitted:
 
 ```rust
 use std::convert::Infallible;
-pub fn safe_unwrap<T>(x: Result<T, Infallible>) -> T {
+pub fn unwrap_without_panic<T>(x: Result<T, Infallible>) -> T {
     let Ok(x) = x; // the `Err` case does not need to appear
     x
 }
 ```
 
 This works with empty types such as a variant-less `enum Void {}`, or structs and enums with a visible empty field and no `#[non_exhaustive]` attribute. It will also be particularly useful in combination with the never type `!`, although that type is still unstable at this time.
 
-This feature is "minimal" because there are still some exclusions at this time. For reasons related to uninitialized values and unsafe code, omitting patterns is not allowed if the empty type is accessed through a reference, pointer, or union field:
+There are still some cases where empty patterns must still be written. For reasons related to uninitialized values and unsafe code, omitting patterns is not allowed if the empty type is accessed through a reference, pointer, or union field:
 
 ```rust
-pub fn safe_unwrap_ref<T>(x: &Result<T, Infallible>) -> &T {
+pub fn unwrap_ref_without_panic<T>(x: &Result<T, Infallible>) -> &T {
     match x {
         Ok(x) => x,
-        // this branch cannot be omitted because of the reference
+        // this arm cannot be omitted because of the reference
         Err(infallible) => match *infallible {},
     }
 }
 ```
 
-To avoid interfering with crates that wish to support several rust versions, branches with empty patterns are not yet warned as "unreachable", despite the fact that they can be removed.
+To avoid interfering with crates that wish to support several Rust versions, `match` arms with empty patterns are not yet reported as “unreachable code” warnings, despite the fact that they can be removed.
 
 ### Floating-point NaN semantics and `const`