From b754b8fb8eaa580753ea3f7bc52fa221cef2a9fe Mon Sep 17 00:00:00 2001 From: Chris Gregory Date: Sat, 13 Apr 2019 15:54:57 -0500 Subject: [PATCH] Expand note on mutable references --- src/libcore/pin.rs | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/libcore/pin.rs b/src/libcore/pin.rs index e1fe0044cc48..d1ebe5ed72ad 100644 --- a/src/libcore/pin.rs +++ b/src/libcore/pin.rs @@ -176,7 +176,10 @@ //! i.e., an operation with type `fn(Pin<&Struct>) -> Pin<&Field>`? In a //! similar vein, when can a generic wrapper type (such as `Vec`, `Box`, //! or `RefCell`) have an operation with type `fn(Pin<&Wrapper>) -> -//! Pin<&T>` (or similarly `fn(Pin<&mut Wrapper>) -> Pin<&mut T>`)? +//! Pin<&T>`? +//! +//! Note: For the entirety of this discussion, the same applies for mutable references as it +//! does for shared references. //! //! Having a pinning projection for some field means that pinning is "structural": //! when the wrapper is pinned, the field must be considered pinned, too.