diff options
| author | Ralf Jung <post@ralfj.de> | 2019-02-21 16:05:49 +0100 |
|---|---|---|
| committer | Ralf Jung <post@ralfj.de> | 2019-02-21 16:05:49 +0100 |
| commit | 32a9614a4e466d5b27227948c9500743066628c8 (patch) | |
| tree | 5a6e3a30112a3cdc7f6d55789c987816866edcdd | |
| parent | 6b880074734e1916f6347d46de28fa44b1f1bae2 (diff) | |
this is for you, tidy
| -rw-r--r-- | src/libcore/pin.rs | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/libcore/pin.rs b/src/libcore/pin.rs index 697c352550f..ff10c33681d 100644 --- a/src/libcore/pin.rs +++ b/src/libcore/pin.rs @@ -15,8 +15,8 @@ //! moving the values they contain: you can move out of a `Box<T>`, or you can use [`mem::swap`]. //! [`Pin<P>`] wraps a pointer type `P`, so `Pin<Box<T>>` functions much like a regular `Box<T>`: //! when a `Pin<Box<T>>` gets dropped, so do its contents, and the memory gets deallocated. -//! Similarily, `Pin<&mut T>` is a lot like `&mut T`. However, [`Pin<P>`] does not let clients actually -//! obtain a `Box<T>` or `&mut T` to pinned data, which implies that you cannot use +//! Similarily, `Pin<&mut T>` is a lot like `&mut T`. However, [`Pin<P>`] does not let clients +//! actually obtain a `Box<T>` or `&mut T` to pinned data, which implies that you cannot use //! operations such as [`mem::swap`]: //! ``` //! use std::pin::Pin; |
