about summary refs log tree commit diff
path: root/src/libstd/thread
diff options
context:
space:
mode:
Diffstat (limited to 'src/libstd/thread')
-rw-r--r--src/libstd/thread/mod.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libstd/thread/mod.rs b/src/libstd/thread/mod.rs
index 5a936da05fd..a95ebb00714 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`] trait.
+/// the [`Error`](std::error::Error) trait.
 ///
 /// Thus, a sensible way to handle a thread panic is to either:
 /// 1. `unwrap` the `Result<T>`, propagating the panic