From: Ralf Jung Date: Wed, 27 Nov 2019 07:53:48 +0000 (+0100) Subject: note that this is all unstable internal details X-Git-Url: https://git.ralfj.de/web.git/commitdiff_plain/c89c36772dcf86fecf1a7360bd81da746f864333?ds=sidebyside note that this is all unstable internal details --- diff --git a/ralf/_posts/2019-11-25-how-to-panic-in-rust.md b/ralf/_posts/2019-11-25-how-to-panic-in-rust.md index 3aa147a..3f5e2f1 100644 --- a/ralf/_posts/2019-11-25-how-to-panic-in-rust.md +++ b/ralf/_posts/2019-11-25-how-to-panic-in-rust.md @@ -18,6 +18,9 @@ There [are still some rough edges](https://github.com/rust-lang/miri/issues?q=is The purpose of this post is to document the high-level structure and the relevant interfaces that come into play on the Rust side of this. The actual mechanism of unwinding is a totally different matter (and one that I am not qualified to speak about). +*Note:* This post describes panicking as of [this commit](https://github.com/rust-lang/rust/commit/7d761fe0462ba0f671a237d0bb35e3579b8ba0e8). +Many of the interfaces described here are unstable internal details of libstd, and subject to change any time. + ## 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.