From e92edb1a53227de283c744200d33bead5eb909ef Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Wed, 27 Nov 2019 08:53:48 +0100 Subject: [PATCH] note that this is all unstable internal details --- personal/_posts/2019-11-25-how-to-panic-in-rust.md | 3 +++ 1 file changed, 3 insertions(+) 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 3aa147a..3f5e2f1 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 @@ -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. -- 2.30.2