8000 docs(library/core/src/pin): fix typo "necessarily" -> "necessary" by ruancomelli · Pull Request #139749 · rust-lang/rust · GitHub
[go: up one dir, main page]
Skip to content

docs(library/core/src/pin): fix typo "necessarily" -> "necessary" #139749

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 16, 2025
Merged

docs(library/core/src/pin): fix typo "necessarily" -> "necessary" #139749

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
14662fa
docs(library/core/src/pin): fix typo "necessarily" -> "necessary"
ruancomelli Apr 13, 2025
6f23f16
docs(library/core/src/pin): rewrite for clarity
ruancomelli Apr 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
docs(library/core/src/pin): rewrite for clarity
  • Loading branch information
@ruancomelli
ruancomelli committed Apr 13, 2025
commit 6f23f167af57af26543fa93f87a12f637e66c5e8
10 changes: 5 additions & 5 deletions library/core/src/pin.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,11 +12,11 @@
//! "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
//! pinned value is still valid. [As we'll see later][drop-guarantee], this is necessary 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
//! intrusive data structures which cannot currently be modeled in fully safe Rust using only
//! borrow-checked [references][reference].
//! pinned value is still valid. [As we'll see later][drop-guarantee], once a value is pinned,
//! it is necessarily valid at its memory location 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 intrusive data structures which cannot currently be modeled in fully safe Rust using
//! only borrow-checked [references][reference].
//!
//! "Pinning" allows us to put a *value* which exists at some location in memory into a state where
//! safe code cannot *move* that value to a different location in memory or otherwise invalidate it
Expand Down
Loading
0