We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
1 parent e9c9d1c commit b754b8fCopy full SHA for b754b8f
src/libcore/pin.rs
@@ -176,7 +176,10 @@
176
//! i.e., an operation with type `fn(Pin<&Struct>) -> Pin<&Field>`? In a
177
//! similar vein, when can a generic wrapper type (such as `Vec<T>`, `Box<T>`,
178
//! or `RefCell<T>`) have an operation with type `fn(Pin<&Wrapper<T>>) ->
179
-//! Pin<&T>` (or similarly `fn(Pin<&mut Wrapper<T>>) -> Pin<&mut T>`)?
+//! Pin<&T>`?
180
+//!
181
+//! Note: For the entirety of this discussion, the same applies for mutable references as it
182
+//! does for shared references.
183
//!
184
//! Having a pinning projection for some field means that pinning is "structural":
185
//! when the wrapper is pinned, the field must be considered pinned, too.
0 commit comments