Add small clarification around using pointers derived from references
Signed-off-by: Alex Saveau <saveau.alexandre@gmail.com>
This commit is contained in:
parent
4827ceecb9
commit
28ea002340
1 changed files with 2 additions and 2 deletions
|
@ -35,7 +35,8 @@
|
|||
//! be used for inter-thread synchronization.
|
||||
//! * The result of casting a reference to a pointer is valid for as long as the
|
||||
//! underlying object is live and no reference (just raw pointers) is used to
|
||||
//! access the same memory.
|
||||
//! access the same memory. That is, reference and pointer accesses cannot be
|
||||
//! interleaved.
|
||||
//!
|
||||
//! These axioms, along with careful use of [`offset`] for pointer arithmetic,
|
||||
//! are enough to correctly implement many useful things in unsafe code. Stronger guarantees
|
||||
|
@ -64,7 +65,6 @@
|
|||
//! separate allocated object), heap allocations (each allocation created by the global allocator is
|
||||
//! a separate allocated object), and `static` variables.
|
||||
//!
|
||||
//!
|
||||
//! # Strict Provenance
|
||||
//!
|
||||
//! **The following text is non-normative, insufficiently formal, and is an extremely strict
|
||||
|
|
Loading…
Add table
Reference in a new issue