rust
/
nomicon
mirror of https://github.com/rust-lang/nomicon
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Replace catch_panic by catch_unwind

Browse Source
pull/217/head
Daniel Bonniot de Ruisselet 5 years ago committed by Alexis Beingessner
parent 4d2d275997
commit 76d0799a8d
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File

4
src/unwinding.md
Unescape View File

@ -31,7 +31,7 @@ panics can only be caught by the parent thread. This means catching a panic
requires spinning up an entire OS thread! This unfortunately stands in conflict requires spinning up an entire OS thread! This unfortunately stands in conflict
to Rust's philosophy of zero-cost abstractions. to Rust's philosophy of zero-cost abstractions.
There is an API called `catch_panic` that enables catching a panic There is an API called [`catch_unwind`][catch_unwind] that enables catching a panic
without spawning a thread. Still, we would encourage you to only do this without spawning a thread. Still, we would encourage you to only do this
sparingly. In particular, Rust's current unwinding implementation is heavily sparingly. In particular, Rust's current unwinding implementation is heavily
optimized for the "doesn't unwind" case. If a program doesn't unwind, there optimized for the "doesn't unwind" case. If a program doesn't unwind, there
@ -47,3 +47,5 @@ You must *absolutely* catch any panics at the FFI boundary! What you do at that
point is up to you, but *something* must be done. If you fail to do this, point is up to you, but *something* must be done. If you fail to do this,
at best, your application will crash and burn. At worst, your application *won't* at best, your application will crash and burn. At worst, your application *won't*
crash and burn, and will proceed with completely clobbered state. crash and burn, and will proceed with completely clobbered state.
[catch_unwind]: https://doc.rust-lang.org/std/panic/fn.catch_unwind.html

Write Preview
Loading…
Cancel
Save