diff options
| author | Manish Goregaokar <manishsmail@gmail.com> | 2024-01-07 08:57:23 -0800 |
|---|---|---|
| committer | Manish Goregaokar <manishsmail@gmail.com> | 2024-01-07 08:57:23 -0800 |
| commit | 7fd841c098e58a69808610e4e89366c03c5621fc (patch) | |
| tree | dee6aa82b33ab712749b3b0f3da0901b19ca64d8 | |
| parent | df6d44961d6f05b7c51189dcce3b05c4fb9ced63 (diff) | |
| download | rust-7fd841c098e58a69808610e4e89366c03c5621fc.tar.gz rust-7fd841c098e58a69808610e4e89366c03c5621fc.zip | |
link
| -rw-r--r-- | library/core/src/pin.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/library/core/src/pin.rs b/library/core/src/pin.rs index ef29e3f373a..bb6c81a486a 100644 --- a/library/core/src/pin.rs +++ b/library/core/src/pin.rs @@ -11,7 +11,7 @@ //! is called "pinning." We would say that a value which satisfies these guarantees has been //! "pinned," in that it has been permanently (until the end of its lifespan) attached to its //! location in memory, as though pinned to a pinboard. Pinning a value is an incredibly useful -//! building block for [unsafe] code to be able to reason about whether a raw pointer to the +//! building block for [`unsafe`] code to be able to reason about whether a raw pointer to the //! pinned value is still valid. [As we'll see later][drop-guarantee], this is necessarily from the //! time the value is first pinned until the end of its lifespan. This concept of "pinning" is //! necessary to implement safe interfaces on top of things like self-referential types and |
