Fix doc link to Instant sub in saturating caveat

rust-lang · jhpratt · May 27, 2026 · May 31, 2026 · Jun 1, 2026 · Jun 2, 2026
commit 6a0f2d4772b5d806d8b98d4409f4acf06d1e3554
diff --git a/library/std/src/time.rs b/library/std/src/time.rs
@@ -137,9 +137,9 @@ use crate::sys::{FromInner, IntoInner, time};
 /// if available, which is the case for all [tier 1] platforms.
 /// In practice such guarantees are – under rare circumstances – broken by hardware, virtualization
 /// or operating system bugs. To work around these bugs and platforms not offering monotonic clocks
-/// [`duration_since`], [`elapsed`] and [`sub`] saturate to zero. In older Rust versions this
-/// lead to a panic instead. [`checked_duration_since`] can be used to detect and handle situations
-/// where monotonicity is violated, or `Instant`s are subtracted in the wrong order.
+/// [`duration_since`], [`elapsed`] and [`sub`](#impl-Sub-for-Instant) saturate to zero. In older
+/// Rust versions this lead to a panic instead. [`checked_duration_since`] can be used to detect and
+/// handle situations where monotonicity is violated, or `Instant`s are subtracted in the wrong order.
 ///
 /// This workaround obscures programming errors where earlier and later instants are accidentally
 /// swapped. For this reason future Rust versions may reintroduce panics.