diff options
| author | nyanpasu64 <nyanpasu64@tuta.io> | 2022-04-10 12:41:31 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-04-10 12:41:31 -0700 |
| commit | bb3a071df8d75bad5e6fecb54ec61477ded777c3 (patch) | |
| tree | a4118faf43bdd23a9787591733b1e4847244bbb7 | |
| parent | 18f32b73bdb3833c18c73fe3062bde8e1721ccca (diff) | |
| download | rust-bb3a071df8d75bad5e6fecb54ec61477ded777c3.tar.gz rust-bb3a071df8d75bad5e6fecb54ec61477ded777c3.zip | |
Fix formatting error in pin.rs docs
| -rw-r--r-- | library/core/src/pin.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/library/core/src/pin.rs b/library/core/src/pin.rs index cef6a68b4d3..720317b05e0 100644 --- a/library/core/src/pin.rs +++ b/library/core/src/pin.rs @@ -175,7 +175,7 @@ //! relies on pinning requires unsafe code, but be aware that deciding to make //! use of pinning in your type (for example by implementing some operation on //! <code>[Pin]<[&]Self></code> or <code>[Pin]<[&mut] Self></code>) has consequences for your -//! [`Drop`][Drop]implementation as well: if an element of your type could have been pinned, +//! [`Drop`][Drop] implementation as well: if an element of your type could have been pinned, //! you must treat [`Drop`][Drop] as implicitly taking <code>[Pin]<[&mut] Self></code>. //! //! For example, you could implement [`Drop`][Drop] as follows: |