about summary refs log tree commit diff
diff options
context:
space:
mode:
authorRalf Jung <post@ralfj.de>2019-08-08 21:02:11 +0200
committerRalf Jung <post@ralfj.de>2019-08-08 21:02:11 +0200
commitfa58c278300895aad254342c89aafa7c080877b3 (patch)
tree211579999df0e0d2c06ecb6338524952553fd9ef
parente82b053f56d11c944c227cefa6d2c2689346d49e (diff)
downloadrust-fa58c278300895aad254342c89aafa7c080877b3.tar.gz
rust-fa58c278300895aad254342c89aafa7c080877b3.zip
remove confusing remark
-rw-r--r--src/libcore/pin.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libcore/pin.rs b/src/libcore/pin.rs
index 251dc4c3b99..271ddcc4662 100644
--- a/src/libcore/pin.rs
+++ b/src/libcore/pin.rs
@@ -188,7 +188,7 @@
 //! you do not accidentally use `self`/`this` in a way that is in conflict with pinning.
 //!
 //! Moreover, if your type is `#[repr(packed)]`, the compiler will automatically
-//! move fields around to be able to drop them. In a packed struct, it might even do
+//! move fields around to be able to drop them. It might even do
 //! that for fields that happen to be sufficiently aligned. As a consequence, you cannot use
 //! pinning with a `#[repr(packed)]` type.
 //!