We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent c7b206b commit 4916314Copy full SHA for 4916314
1 file changed
library/core/src/pin.rs
@@ -600,7 +600,7 @@
600
//! automatically called [`Pin::get_unchecked_mut`].
601
//!
602
//! This can never cause a problem in purely safe code because creating a pinning pointer to
603
-//! a type which has an address-sensitive (thus does not implement `Unpin`) requires `unsafe`,
+//! a type which has address-sensitive states (and thus does not implement `Unpin`) requires `unsafe`,
604
//! but it is important to note that choosing to take advantage of pinning-related guarantees
605
//! to justify validity in the implementation of your type has consequences for that type's
606
//! [`Drop`][Drop] implementation as well: if an element of your type could have been pinned,
0 commit comments