how-to-panic: link to ongoing cleanup effort

[web.git] / 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 f840aa65ece45539d8284c5e53ada40db5ac5be7..ad4589d0ac06b6e4ab3ae015409468f04e82a119 100644 (file)
--- 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.
 
 *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.
 ## 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.