diff options
| author | Alcaro <floating@muncher.se> | 2024-08-31 19:09:41 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-08-31 19:09:41 +0200 |
| commit | 7d728e54d97c6062c3ad2ccbc6ac48faa99bce31 (patch) | |
| tree | f28cf65bbb025adeab778734b412bb0fa9db1494 | |
| parent | 9649706eada1b2c68cf6504356efb058f68ad739 (diff) | |
| download | rust-7d728e54d97c6062c3ad2ccbc6ac48faa99bce31.tar.gz rust-7d728e54d97c6062c3ad2ccbc6ac48faa99bce31.zip | |
Update mod.rs
This typo looks unnecessary
| -rw-r--r-- | library/core/src/mem/mod.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/library/core/src/mem/mod.rs b/library/core/src/mem/mod.rs index e602b497d17..fed484ae3cd 100644 --- a/library/core/src/mem/mod.rs +++ b/library/core/src/mem/mod.rs @@ -612,7 +612,7 @@ pub const fn needs_drop<T: ?Sized>() -> 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` +/// for reference types (`&T`, `&mut T`) and function 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. |
