X-Git-Url: https://git.ralfj.de/web.git/blobdiff_plain/317ebd9167f15892e966c0c3dbcfc7077bf47d42..27452daa29f8757e4249c6f63e6487ecb100fa7e:/personal/_posts/2019-11-25-how-to-panic-in-rust.md

diff --git a/personal/_posts/2019-11-25-how-to-panic-in-rust.md b/personal/_posts/2019-11-25-how-to-panic-in-rust.md
index f840aa6..ad4589d 100644
--- a/personal/_posts/2019-11-25-how-to-panic-in-rust.md
+++ b/personal/_posts/2019-11-25-how-to-panic-in-rust.md
@@ -21,6 +21,9 @@ The actual mechanism of unwinding is a totally different matter (and one that I
 *Note:* This post describes panicking as of [this commit](https://github.com/rust-lang/rust/commit/4007d4ef26eab44bdabc2b7574d032152264d3ad).
 Many of the interfaces described here are unstable internal details of libstd, and subject to change any time.
 
+*Update (2025-08-18):* As expected, many parts of this post are quite outdated by now.
+See [here](https://github.com/rust-lang/rust/issues/116005) for an issue tracking the ongoing cleanup effort of the panic machinery.
+
 ## High-level structure
 
 When trying to figure out how panicking works by reading the code in libstd, one can easily get lost in the maze.