diff options
| author | David Tolnay <dtolnay@gmail.com> | 2020-06-17 17:17:07 -0700 |
|---|---|---|
| committer | David Tolnay <dtolnay@gmail.com> | 2020-06-17 17:17:07 -0700 |
| commit | 2da9ca72bcdc6b67fbacf26d9245da367089a113 (patch) | |
| tree | 8ea4bff3ab981a8d09759a519e23f893e4c8f8bf /src/libcore | |
| parent | e75fa896ba53eb5fc5c3dd2741101f377488c2db (diff) | |
| download | rust-2da9ca72bcdc6b67fbacf26d9245da367089a113.tar.gz rust-2da9ca72bcdc6b67fbacf26d9245da367089a113.zip | |
Remove duplicate sentence fragment from mem::zeroed doc
Diffstat (limited to 'src/libcore')
| -rw-r--r-- | src/libcore/mem/mod.rs | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/src/libcore/mem/mod.rs b/src/libcore/mem/mod.rs index 70083ffa4be..066bb8b3dc7 100644 --- a/src/libcore/mem/mod.rs +++ b/src/libcore/mem/mod.rs @@ -583,10 +583,10 @@ pub const fn needs_drop<T>() -> bool { /// /// There is no guarantee that an all-zero byte-pattern represents a valid value /// of some type `T`. For example, the all-zero byte-pattern is not a valid value -/// for reference types (`&T`, `&mut T`) and functions pointers. Using `zeroed` on -/// such types on such types causes immediate [undefined behavior][ub] because -/// [the Rust compiler assumes][inv] that there always is a valid value in a -/// variable it considers initialized. +/// for reference types (`&T`, `&mut T`) and functions pointers. Using `zeroed` +/// on such types causes immediate [undefined behavior][ub] because [the Rust +/// compiler assumes][inv] that there always is a valid value in a variable it +/// considers initialized. /// /// This has the same effect as [`MaybeUninit::zeroed().assume_init()`][zeroed]. /// It is useful for FFI sometimes, but should generally be avoided. |
