Update the description of alloc error handling

Co-authored-by: Mark Rousskov <mark.simulacrum@gmail.com>

Author: cuviper

posts/2023-03-09-Rust-1.68.0.md

@@ -95,13 +95,12 @@ subject to the normal borrow checker to make sure it can't outlive that local.
 
 When allocation fails in Rust, APIs like `Box::new` and `Vec::push` have no way
 to indicate that failure, so some divergent execution path needs to be taken.
-When using the `std` crate, the program will print to `stderr` and abort. But
-with `#![no_std]` and the `alloc` crate, it was required to provide a
-`#[alloc_error_handler]` function, similar to `#[panic_handler]`, but that
-attribute is still unstable.
+When using the `std` crate, the program will print to `stderr` and abort.
+As of Rust 1.68.0, binaries which include `std` will continue to have
+this behavior. Binaries which do not include `std`, only including `alloc`, will now `panic!`
+on allocation failure, which may be further adjusted via a `#[panic_handler]` if desired.
 
-Now in Rust 1.68.0, a default handler is provided which turns that `alloc` error
-into a `panic!`, which may be processed in a `#[panic_handler]` like any other.
+In the future, it's likely that the behavior for `std` will also be changed to match that of `alloc`-only binaries.
 
 ### Stabilized APIs