File tree Expand file tree Collapse file tree 1 file changed +2
-2
lines changed Expand file tree Collapse file tree 1 file changed +2
-2
lines changed Original file line number Diff line number Diff line change 331331//!
332332//! Note that this invariant is enforced by simply making it impossible to call code that would
333333//! perform a move on the pinned value. This is the case since the only way to access that pinned
334- //! value is through the pinning <code>[Pin]<[&mut] T>> </code>, which in turn restricts our access.
334+ //! value is through the pinning <code>[Pin]<[&mut] T></code>, which in turn restricts our access.
335335//!
336336//! ## [`Unpin`]
337337//!
379379//!
380380//! Exposing access to the inner field which you want to remain pinned must then be carefully
381381//! considered as well! Remember, exposing a method that gives access to a
382- //! <code>[Pin]<[&mut] InnerT>> </code> where <code>InnerT: [Unpin]</code> would allow safe code to
382+ //! <code>[Pin]<[&mut] InnerT></code> where <code>InnerT: [Unpin]</code> would allow safe code to
383383//! trivially move the inner value out of that pinning pointer, which is precisely what you're
384384//! seeking to prevent! Exposing a field of a pinned value through a pinning pointer is called
385385//! "projecting" a pin, and the more general case of deciding in which cases a pin should be able
You can’t perform that action at this time.
0 commit comments