mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

tweak wording regarding Box validity

Browse Source
This commit is contained in:
Ralf Jung 2024-09-01 11:21:37 +02:00
parent 05ffd446a9
commit 0e5628d7de
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
library/alloc/src/boxed.rs
View File

@ -64,8 +64,9 @@
//! //!
//! For zero-sized values, the `Box` pointer has to be non-null and sufficiently aligned. The //! For zero-sized values, the `Box` pointer has to be non-null and sufficiently aligned. The
//! recommended way to build a Box to a ZST if `Box::new` cannot be used is to use //! recommended way to build a Box to a ZST if `Box::new` cannot be used is to use
//! [`ptr::NonNull::dangling`]. Even for zero-sized types, the pointee type must be inhabited //! [`ptr::NonNull::dangling`].
//! to ensure that the Box points to a valid value of the given type. //!
//! On top of these basic layout requirements, a `Box<T>` must point to a valid value of `T`.
//! //!
//! So long as `T: Sized`, a `Box<T>` is guaranteed to be represented //! So long as `T: Sized`, a `Box<T>` is guaranteed to be represented
//! as a single pointer and is also ABI-compatible with C pointers //! as a single pointer and is also ABI-compatible with C pointers