File tree 1 file changed +3
-2
lines changed
1 file changed +3
-2
lines changed Original file line number Diff line number Diff line change
1
+ Agent pid 43580
1
2
//! Types that pin data to a location in memory.
2
3
//!
3
4
//! It is sometimes useful to be able to rely upon a certain value not being able to *move*,
331
332
//!
332
333
//! Note that this invariant is enforced by simply making it impossible to call code that would
333
334
//! 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.
335
+ //! value is through the pinning <code>[Pin]<[&mut] T></code>, which in turn restricts our access.
335
336
//!
336
337
//! ## [`Unpin`]
337
338
//!
379
380
//!
380
381
//! Exposing access to the inner field which you want to remain pinned must then be carefully
381
382
//! 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
383
+ //! <code>[Pin]<[&mut] InnerT></code> where <code>InnerT: [Unpin]</code> would allow safe code to
383
384
//! trivially move the inner value out of that pinning pointer, which is precisely what you're
384
385
//! seeking to prevent! Exposing a field of a pinned value through a pinning pointer is called
385
386
//! "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