diff options
| author | Sebastian Dröge <sebastian@centricular.com> | 2017-11-02 18:30:02 +0200 |
|---|---|---|
| committer | Sebastian Dröge <sebastian@centricular.com> | 2017-11-02 18:33:25 +0200 |
| commit | a12f5119101060909de1938d7d4a96854cc02780 (patch) | |
| tree | ea284cb3b98336a90071651fd704be74e258d184 /src/libstd/thread | |
| parent | 283b4a1b0bcf94fed0ebc3bfd84e87d17ca1b587 (diff) | |
| download | rust-a12f5119101060909de1938d7d4a96854cc02780.tar.gz rust-a12f5119101060909de1938d7d4a96854cc02780.zip | |
Mention that panics can't possibly be caught when compiling with panic=abort
Diffstat (limited to 'src/libstd/thread')
| -rw-r--r-- | src/libstd/thread/mod.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libstd/thread/mod.rs b/src/libstd/thread/mod.rs index da5965d801c..97220ad993b 100644 --- a/src/libstd/thread/mod.rs +++ b/src/libstd/thread/mod.rs @@ -26,7 +26,7 @@ //! Fatal logic errors in Rust cause *thread panic*, during which //! a thread will unwind the stack, running destructors and freeing //! owned resources. While not meant as a 'try/catch' mechanism, panics -//! in Rust can nonetheless be caught with +//! in Rust can nonetheless be caught (unless compiling with `panic=abort`) with //! [`catch_unwind`](../../std/panic/fn.catch_unwind.html) and recovered //! from, or alternatively be resumed with //! [`resume_unwind`](../../std/panic/fn.resume_unwind.html). If the panic |