diff options
| author | Pyry Kontio <pyry.kontio@drasa.eu> | 2019-11-07 01:45:30 +0900 |
|---|---|---|
| committer | Pyry Kontio <kontio@r.recruit.co.jp> | 2019-11-07 01:45:46 +0900 |
| commit | 8568204f4e934ff93817f948b13a9c804277a6bf (patch) | |
| tree | 84b73520d13cbdb505d63a9618d4374d4002d234 /src/libstd/thread | |
| parent | 4317263a311ad4adc54529b5fdcfe1e18fb651be (diff) | |
| download | rust-8568204f4e934ff93817f948b13a9c804277a6bf.tar.gz rust-8568204f4e934ff93817f948b13a9c804277a6bf.zip | |
Try with crate::error::Error
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 a95ebb00714..0c632d2afbd 100644 --- a/src/libstd/thread/mod.rs +++ b/src/libstd/thread/mod.rs @@ -1275,7 +1275,7 @@ impl fmt::Debug for Thread { /// is the value the thread panicked with; /// that is, the argument the `panic!` macro was called with. /// Unlike with normal errors, this value doesn't implement -/// the [`Error`](std::error::Error) trait. +/// the [`Error`](crate::error::Error) trait. /// /// Thus, a sensible way to handle a thread panic is to either: /// 1. `unwrap` the `Result<T>`, propagating the panic |