File tree 1 file changed +4
-4
lines changed
1 file changed +4
-4
lines changed Original file line number Diff line number Diff line change @@ -583,10 +583,10 @@ pub const fn needs_drop<T>() -> bool {
583
583
///
584
584
/// There is no guarantee that an all-zero byte-pattern represents a valid value
585
585
/// of some type `T`. For example, the all-zero byte-pattern is not a valid value
586
- /// for reference types (`&T`, `&mut T`) and functions pointers. Using `zeroed` on
587
- /// such types on such types causes immediate [undefined behavior][ub] because
588
- /// [the Rust compiler assumes][inv] that there always is a valid value in a
589
- /// variable it considers initialized.
586
+ /// for reference types (`&T`, `&mut T`) and functions pointers. Using `zeroed`
587
+ /// on such types causes immediate [undefined behavior][ub] because [the Rust
588
+ /// compiler assumes][inv] that there always is a valid value in a variable it
589
+ /// considers initialized.
590
590
///
591
591
/// This has the same effect as [`MaybeUninit::zeroed().assume_init()`][zeroed].
592
592
/// It is useful for FFI sometimes, but should generally be avoided.
You can’t perform that action at this time.
0 commit comments