about summary refs log tree commit diff
path: root/src/libstd/thread
diff options
context:
space:
mode:
authorPyry Kontio <pyry.kontio@drasa.eu>2019-11-06 16:57:59 +0900
committerPyry Kontio <kontio@r.recruit.co.jp>2019-11-06 16:59:53 +0900
commit4317263a311ad4adc54529b5fdcfe1e18fb651be (patch)
tree1f4565dffc8c6d8fc6d76e5739839885ab71d8e7 /src/libstd/thread
parentf1bc4ef170dc27f7c186e6b00de30f66eee14f6c (diff)
downloadrust-4317263a311ad4adc54529b5fdcfe1e18fb651be.tar.gz
rust-4317263a311ad4adc54529b5fdcfe1e18fb651be.zip
Fix the Error linking.
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