From df6d44961d6f05b7c51189dcce3b05c4fb9ced63 Mon Sep 17 00:00:00 2001 From: Manish Goregaokar Date: Sun, 7 Jan 2024 08:33:14 -0800 Subject: [PATCH] Update library/core/src/pin.rs Co-authored-by: Ralf Jung --- library/core/src/pin.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/library/core/src/pin.rs b/library/core/src/pin.rs index 15f5d7ce19c..ef29e3f373a 100644 --- a/library/core/src/pin.rs +++ b/library/core/src/pin.rs @@ -790,7 +790,7 @@ //! //! Structural pinning comes with a few extra requirements: //! -//! 1. *Structural [`Unpin`].* A struct can be [`Unpin`] if, and only if, all of its +//! 1. *Structural [`Unpin`].* A struct can be [`Unpin`] only if all of its //! structurally-pinned fields are, too. This is [`Unpin`]'s behavior by default. //! However, as a libray author, it is your responsibility not to write something like //! impl\ [Unpin] for Struct\ {} and then offer a method that provides