diff options
| author | Pyry Kontio <pyry.kontio@drasa.eu> | 2019-11-06 14:47:52 +0900 |
|---|---|---|
| committer | Pyry Kontio <kontio@r.recruit.co.jp> | 2019-11-06 14:48:23 +0900 |
| commit | f1bc4ef170dc27f7c186e6b00de30f66eee14f6c (patch) | |
| tree | c93f3598afb85bbf3664ea4236557c35466f7b5c /src/libstd/thread | |
| parent | 002c1c74d99295e49e30a02fb98f25383f1576f8 (diff) | |
| download | rust-f1bc4ef170dc27f7c186e6b00de30f66eee14f6c.tar.gz rust-f1bc4ef170dc27f7c186e6b00de30f66eee14f6c.zip | |
Addressed review comments.
Diffstat (limited to 'src/libstd/thread')
| -rw-r--r-- | src/libstd/thread/mod.rs | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/src/libstd/thread/mod.rs b/src/libstd/thread/mod.rs index 2af0a4804ef..5a936da05fd 100644 --- a/src/libstd/thread/mod.rs +++ b/src/libstd/thread/mod.rs @@ -1273,15 +1273,15 @@ impl fmt::Debug for Thread { /// /// The value contained in the `Result::Err` variant /// is the value the thread panicked with; -/// that is, the parameter the `panic!` macro was called with. +/// that is, the argument the `panic!` macro was called with. /// Unlike with normal errors, this value doesn't implement -/// the `std::error::Error` trait. +/// the [`Error`] trait. /// -/// Thus, a sensible way to handle a thread panic is to either -/// `unwrap` the `Result`, propagating the panic, -/// or in case the thread is intended to be a subsystem boundary +/// Thus, a sensible way to handle a thread panic is to either: +/// 1. `unwrap` the `Result<T>`, propagating the panic +/// 2. or in case the thread is intended to be a subsystem boundary /// that is supposed to isolate system-level failures, -/// match for the `Err` variant and handle the panic in an appropriate way. +/// match on the `Err` variant and handle the panic in an appropriate way. /// /// A thread that completes without panicking is considered to exit successfully. /// |
