diff options
| author | Nathan VanBenschoten <nvanbenschoten@gmail.com> | 2025-01-24 23:26:02 -0700 |
|---|---|---|
| committer | Nathan VanBenschoten <nvanbenschoten@gmail.com> | 2025-01-24 23:26:02 -0700 |
| commit | 83c09ff3bd5a390bc7f4968e4e570744d11d4663 (patch) | |
| tree | f84ef4f4de17b84c00a7d52d3ba43bbc1f67c6cd /library/core/src | |
| parent | 814ebca2931bd25384ade5018e1cbc403b13ec11 (diff) | |
docs: fix typo in std::pin overview
Diffstat (limited to 'library/core/src')
| -rw-r--r-- | library/core/src/pin.rs | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/library/core/src/pin.rs b/library/core/src/pin.rs index 71044190f0c..2a0bf89fcf7 100644 --- a/library/core/src/pin.rs +++ b/library/core/src/pin.rs @@ -156,8 +156,8 @@ //! //! In order to implement the second option, we must in some way enforce its key invariant, //! *i.e.* prevent the value from being *moved* or otherwise invalidated (you may notice this -//! sounds an awful lot like the definition of *pinning* a value). There a few ways one might be -//! able to enforce this invariant in Rust: +//! sounds an awful lot like the definition of *pinning* a value). There are a few ways one might +//! be able to enforce this invariant in Rust: //! //! 1. Offer a wholly `unsafe` API to interact with the object, thus requiring every caller to //! uphold the invariant themselves |
