Skip to content

Commit 9c18fe0

Browse files
committed
fix typo in typenames of pin documentation
1 parent 8c39ce5 commit 9c18fe0

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

library/core/src/pin.rs

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
Agent pid 43580
12
//! Types that pin data to a location in memory.
23
//!
34
//! It is sometimes useful to be able to rely upon a certain value not being able to *move*,
@@ -331,7 +332,7 @@
331332
//!
332333
//! Note that this invariant is enforced by simply making it impossible to call code that would
333334
//! 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.
335336
//!
336337
//! ## [`Unpin`]
337338
//!
@@ -379,7 +380,7 @@
379380
//!
380381
//! Exposing access to the inner field which you want to remain pinned must then be carefully
381382
//! 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
383384
//! trivially move the inner value out of that pinning pointer, which is precisely what you're
384385
//! seeking to prevent! Exposing a field of a pinned value through a pinning pointer is called
385386
//! "projecting" a pin, and the more general case of deciding in which cases a pin should be able

0 commit comments

Comments
 (0)