about summary refs log tree commit diff
diff options
context:
space:
mode:
authorAlisa Sireneva <me@purplesyringa.moe>2025-07-25 16:09:29 +0300
committerAlisa Sireneva <me@purplesyringa.moe>2025-07-25 16:09:29 +0300
commitda4687bafe4ff78a9816797c3b74b6bcc0c5a3bc (patch)
tree265c725f493d804bf4a83d066c2b133c03a94ddd
parent5b2c61edbe508163ad11cde0f35278417d7c26b3 (diff)
downloadrust-da4687bafe4ff78a9816797c3b74b6bcc0c5a3bc.tar.gz
rust-da4687bafe4ff78a9816797c3b74b6bcc0c5a3bc.zip
Link to Mutex poisoning docs from RwLock docs
-rw-r--r--library/std/src/sync/poison/rwlock.rs4
1 files changed, 3 insertions, 1 deletions
diff --git a/library/std/src/sync/poison/rwlock.rs b/library/std/src/sync/poison/rwlock.rs
index 0a50b6c2d8f..2c92602bc87 100644
--- a/library/std/src/sync/poison/rwlock.rs
+++ b/library/std/src/sync/poison/rwlock.rs
@@ -46,11 +46,13 @@ use crate::sys::sync as sys;
 ///
 /// # Poisoning
 ///
-/// An `RwLock`, like [`Mutex`], will usually become poisoned on a panic. Note,
+/// An `RwLock`, like [`Mutex`], will [usually] become poisoned on a panic. Note,
 /// however, that an `RwLock` may only be poisoned if a panic occurs while it is
 /// locked exclusively (write mode). If a panic occurs in any reader, then the
 /// lock will not be poisoned.
 ///
+/// [usually]: super::Mutex#poisoning
+///
 /// # Examples
 ///
 /// ```