File tree 1 file changed +2
-2
lines changed
1 file changed +2
-2
lines changed Original file line number Diff line number Diff line change @@ -51,7 +51,7 @@ use crate::mem::ManuallyDrop;
51
51
///
52
52
/// On top of that, remember that most types have additional invariants beyond merely
53
53
/// being considered initialized at the type level. For example, a `1`-initialized [`Vec<T>`]
54
- /// is considered initialized (under the current implementation, this does not constitute
54
+ /// is considered initialized (under the current implementation; this does not constitute
55
55
/// a stable guarantee) because the only requirement the compiler knows about it
56
56
/// is that the data pointer must be non-null. Creating such a `Vec<T>` does not cause
57
57
/// *immediate* undefined behavior, but will cause undefined behavior with most
@@ -405,7 +405,7 @@ impl<T> MaybeUninit<T> {
405
405
///
406
406
/// On top of that, remember that most types have additional invariants beyond merely
407
407
/// being considered initialized at the type level. For example, a `1`-initialized [`Vec<T>`]
408
- /// is considered initialized (under the current implementation, this does not constitute
408
+ /// is considered initialized (under the current implementation; this does not constitute
409
409
/// a stable guarantee) because the only requirement the compiler knows about it
410
410
/// is that the data pointer must be non-null. Creating such a `Vec<T>` does not cause
411
411
/// *immediate* undefined behavior, but will cause undefined behavior with most
You can’t perform that action at this time.
0 commit comments