X-Git-Url: https://git.lizzy.rs/?a=blobdiff_plain;f=src%2Flibcore%2Ffuture%2Ffuture.rs;h=593c01060ca49ae981ce21ceab6423055e85cf30;hb=97098f466ad7a72e6690cf45e6ff2d60885396a9;hp=8bd1601a362133899176df264d1a7373df31f706;hpb=3bbc42114271021fbe6b74766531f08399fc9a0d;p=rust.git

diff --git a/src/libcore/future/future.rs b/src/libcore/future/future.rs
index 8bd1601a362..593c01060ca 100644
--- a/src/libcore/future/future.rs
+++ b/src/libcore/future/future.rs
@@ -17,11 +17,13 @@
 /// final value. This method does not block if the value is not ready. Instead,
 /// the current task is scheduled to be woken up when it's possible to make
 /// further progress by `poll`ing again. The `context` passed to the `poll`
-/// method can provide a `Waker`, which is a handle for waking up the current
+/// method can provide a [`Waker`], which is a handle for waking up the current
 /// task.
 ///
 /// When using a future, you generally won't call `poll` directly, but instead
 /// `.await` the value.
+///
+/// [`Waker`]: ../task/struct.Waker.html
 #[doc(spotlight)]
 #[must_use = "futures do nothing unless you `.await` or poll them"]
 #[stable(feature = "futures_api", since = "1.36.0")]