From 8568204f4e934ff93817f948b13a9c804277a6bf Mon Sep 17 00:00:00 2001
From: Pyry Kontio <pyry.kontio@drasa.eu>
Date: Thu, 7 Nov 2019 01:45:30 +0900
Subject: [PATCH] Try with crate::error::Error

---
 src/libstd/thread/mod.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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