pub struct NonNull<T: ?Sized> { /* private fields */ }
Expand description
*mut T
but non-zero and covariant.
This is often the correct thing to use when building data structures using
raw pointers, but is ultimately more dangerous to use because of its additional
properties. If you’re not sure if you should use NonNull<T>
, just use *mut T
!
Unlike *mut T
, the pointer must always be non-null, even if the pointer
is never dereferenced. This is so that enums may use this forbidden value
as a discriminant – Option<NonNull<T>>
has the same size as *mut T
.
However the pointer may still dangle if it isn’t dereferenced.
Unlike *mut T
, NonNull<T>
was chosen to be covariant over T
. This makes it
possible to use NonNull<T>
when building covariant types, but introduces the
risk of unsoundness if used in a type that shouldn’t actually be covariant.
(The opposite choice was made for *mut T
even though technically the unsoundness
could only be caused by calling unsafe functions.)
Covariance is correct for most safe abstractions, such as Box
, Rc
, Arc
, Vec
,
and LinkedList
. This is the case because they provide a public API that follows the
normal shared XOR mutable rules of Rust.
If your type cannot safely be covariant, you must ensure it contains some
additional field to provide invariance. Often this field will be a PhantomData
type like PhantomData<Cell<T>>
or PhantomData<&'a mut T>
.
Notice that NonNull<T>
has a From
instance for &T
. However, this does
not change the fact that mutating through a (pointer derived from a) shared
reference is undefined behavior unless the mutation happens inside an
UnsafeCell<T>
. The same goes for creating a mutable reference from a shared
reference. When using this From
instance without an UnsafeCell<T>
,
it is your responsibility to ensure that as_mut
is never called, and as_ptr
is never used for mutation.
§Representation
Thanks to the null pointer optimization,
NonNull<T>
and Option<NonNull<T>>
are guaranteed to have the same size and alignment:
use std::ptr::NonNull;
assert_eq!(size_of::<NonNull<i16>>(), size_of::<Option<NonNull<i16>>>());
assert_eq!(align_of::<NonNull<i16>>(), align_of::<Option<NonNull<i16>>>());
assert_eq!(size_of::<NonNull<str>>(), size_of::<Option<NonNull<str>>>());
assert_eq!(align_of::<NonNull<str>>(), align_of::<Option<NonNull<str>>>());
Implementations§
Source§impl<T: Sized> NonNull<T>
impl<T: Sized> NonNull<T>
1.25.0 (const: 1.36.0) · Sourcepub const fn dangling() -> Self
pub const fn dangling() -> Self
Creates a new NonNull
that is dangling, but well-aligned.
This is useful for initializing types which lazily allocate, like
Vec::new
does.
Note that the pointer value may potentially represent a valid pointer to
a T
, which means this must not be used as a “not yet initialized”
sentinel value. Types that lazily allocate must track initialization by
some other means.
§Examples
Sourcepub const unsafe fn as_uninit_ref<'a>(self) -> &'a MaybeUninit<T>
🔬This is a nightly-only experimental API. (ptr_as_uninit
#75402)
pub const unsafe fn as_uninit_ref<'a>(self) -> &'a MaybeUninit<T>
ptr_as_uninit
#75402)Returns a shared references to the value. In contrast to as_ref
, this does not require
that the value has to be initialized.
For the mutable counterpart see as_uninit_mut
.
§Safety
When calling this method, you have to ensure that
the pointer is convertible to a reference.
Note that because the created reference is to MaybeUninit<T>
, the
source pointer can point to uninitialized memory.
Sourcepub const unsafe fn as_uninit_mut<'a>(self) -> &'a mut MaybeUninit<T>
🔬This is a nightly-only experimental API. (ptr_as_uninit
#75402)
pub const unsafe fn as_uninit_mut<'a>(self) -> &'a mut MaybeUninit<T>
ptr_as_uninit
#75402)Returns a unique references to the value. In contrast to as_mut
, this does not require
that the value has to be initialized.
For the shared counterpart see as_uninit_ref
.
§Safety
When calling this method, you have to ensure that
the pointer is convertible to a reference.
Note that because the created reference is to MaybeUninit<T>
, the
source pointer can point to uninitialized memory.
Source§impl<T: ?Sized> NonNull<T>
impl<T: ?Sized> NonNull<T>
1.25.0 (const: 1.25.0) · Sourcepub const unsafe fn new_unchecked(ptr: *mut T) -> Self
pub const unsafe fn new_unchecked(ptr: *mut T) -> Self
1.25.0 (const: 1.85.0) · Sourcepub const fn new(ptr: *mut T) -> Option<Self>
pub const fn new(ptr: *mut T) -> Option<Self>
Creates a new NonNull
if ptr
is non-null.
§Examples
Sourcepub const fn from_ref(r: &T) -> Self
🔬This is a nightly-only experimental API. (non_null_from_ref
#130823)
pub const fn from_ref(r: &T) -> Self
non_null_from_ref
#130823)Converts a reference to a NonNull
pointer.
Sourcepub const fn from_mut(r: &mut T) -> Self
🔬This is a nightly-only experimental API. (non_null_from_ref
#130823)
pub const fn from_mut(r: &mut T) -> Self
non_null_from_ref
#130823)Converts a mutable reference to a NonNull
pointer.
Sourcepub const fn from_raw_parts(
data_pointer: NonNull<impl Thin>,
metadata: <T as Pointee>::Metadata,
) -> NonNull<T>
🔬This is a nightly-only experimental API. (ptr_metadata
#81513)
pub const fn from_raw_parts( data_pointer: NonNull<impl Thin>, metadata: <T as Pointee>::Metadata, ) -> NonNull<T>
ptr_metadata
#81513)Performs the same functionality as std::ptr::from_raw_parts
, except that a
NonNull
pointer is returned, as opposed to a raw *const
pointer.
See the documentation of std::ptr::from_raw_parts
for more details.
Sourcepub const fn to_raw_parts(self) -> (NonNull<()>, <T as Pointee>::Metadata)
🔬This is a nightly-only experimental API. (ptr_metadata
#81513)
pub const fn to_raw_parts(self) -> (NonNull<()>, <T as Pointee>::Metadata)
ptr_metadata
#81513)Decompose a (possibly wide) pointer into its data pointer and metadata components.
The pointer can be later reconstructed with NonNull::from_raw_parts
.
1.84.0 · Sourcepub fn addr(self) -> NonZero<usize>
pub fn addr(self) -> NonZero<usize>
Gets the “address” portion of the pointer.
For more details see the equivalent method on a raw pointer, pointer::addr
.
This is a Strict Provenance API.
1.84.0 · Sourcepub fn with_addr(self, addr: NonZero<usize>) -> Self
pub fn with_addr(self, addr: NonZero<usize>) -> Self
Creates a new pointer with the given address and the provenance of
self
.
For more details see the equivalent method on a raw pointer, pointer::with_addr
.
This is a Strict Provenance API.
1.84.0 · Sourcepub fn map_addr(self, f: impl FnOnce(NonZero<usize>) -> NonZero<usize>) -> Self
pub fn map_addr(self, f: impl FnOnce(NonZero<usize>) -> NonZero<usize>) -> Self
Creates a new pointer by mapping self
’s address to a new one, preserving the
provenance of self
.
For more details see the equivalent method on a raw pointer, pointer::map_addr
.
This is a Strict Provenance API.
1.25.0 (const: 1.32.0) · Sourcepub const fn as_ptr(self) -> *mut T
pub const fn as_ptr(self) -> *mut T
Acquires the underlying *mut
pointer.
§Examples
1.25.0 (const: 1.73.0) · Sourcepub const unsafe fn as_ref<'a>(&self) -> &'a T
pub const unsafe fn as_ref<'a>(&self) -> &'a T
Returns a shared reference to the value. If the value may be uninitialized, as_uninit_ref
must be used instead.
For the mutable counterpart see as_mut
.
§Safety
When calling this method, you have to ensure that the pointer is convertible to a reference.
§Examples
1.25.0 (const: 1.83.0) · Sourcepub const unsafe fn as_mut<'a>(&mut self) -> &'a mut T
pub const unsafe fn as_mut<'a>(&mut self) -> &'a mut T
Returns a unique reference to the value. If the value may be uninitialized, as_uninit_mut
must be used instead.
For the shared counterpart see as_ref
.
§Safety
When calling this method, you have to ensure that the pointer is convertible to a reference.
§Examples
1.27.0 (const: 1.36.0) · Sourcepub const fn cast<U>(self) -> NonNull<U>
pub const fn cast<U>(self) -> NonNull<U>
Casts to a pointer of another type.
§Examples
1.80.0 (const: 1.80.0) · Sourcepub const unsafe fn offset(self, count: isize) -> Selfwhere
T: Sized,
pub const unsafe fn offset(self, count: isize) -> Selfwhere
T: Sized,
Adds an offset to a pointer.
count
is in units of T; e.g., a count
of 3 represents a pointer
offset of 3 * size_of::<T>()
bytes.
§Safety
If any of the following conditions are violated, the result is Undefined Behavior:
-
The computed offset,
count * size_of::<T>()
bytes, must not overflowisize
. -
If the computed offset is non-zero, then
self
must be derived from a pointer to some allocated object, and the entire memory range betweenself
and the result must be in bounds of that allocated object. In particular, this range must not “wrap around” the edge of the address space.
Allocated objects can never be larger than isize::MAX
bytes, so if the computed offset
stays in bounds of the allocated object, it is guaranteed to satisfy the first requirement.
This implies, for instance, that vec.as_ptr().add(vec.len())
(for vec: Vec<T>
) is always
safe.
§Examples
1.80.0 (const: 1.80.0) · Sourcepub const unsafe fn byte_offset(self, count: isize) -> Self
pub const unsafe fn byte_offset(self, count: isize) -> Self
Calculates the offset from a pointer in bytes.
count
is in units of bytes.
This is purely a convenience for casting to a u8
pointer and
using offset on it. See that method for documentation
and safety requirements.
For non-Sized
pointees this operation changes only the data pointer,
leaving the metadata untouched.
1.80.0 (const: 1.80.0) · Sourcepub const unsafe fn add(self, count: usize) -> Selfwhere
T: Sized,
pub const unsafe fn add(self, count: usize) -> Selfwhere
T: Sized,
Adds an offset to a pointer (convenience for .offset(count as isize)
).
count
is in units of T; e.g., a count
of 3 represents a pointer
offset of 3 * size_of::<T>()
bytes.
§Safety
If any of the following conditions are violated, the result is Undefined Behavior:
-
The computed offset,
count * size_of::<T>()
bytes, must not overflowisize
. -
If the computed offset is non-zero, then
self
must be derived from a pointer to some allocated object, and the entire memory range betweenself
and the result must be in bounds of that allocated object. In particular, this range must not “wrap around” the edge of the address space.
Allocated objects can never be larger than isize::MAX
bytes, so if the computed offset
stays in bounds of the allocated object, it is guaranteed to satisfy the first requirement.
This implies, for instance, that vec.as_ptr().add(vec.len())
(for vec: Vec<T>
) is always
safe.
§Examples
1.80.0 (const: 1.80.0) · Sourcepub const unsafe fn byte_add(self, count: usize) -> Self
pub const unsafe fn byte_add(self, count: usize) -> Self
Calculates the offset from a pointer in bytes (convenience for .byte_offset(count as isize)
).
count
is in units of bytes.
This is purely a convenience for casting to a u8
pointer and
using add
on it. See that method for documentation
and safety requirements.
For non-Sized
pointees this operation changes only the data pointer,
leaving the metadata untouched.
1.80.0 (const: 1.80.0) · Sourcepub const unsafe fn sub(self, count: usize) -> Selfwhere
T: Sized,
pub const unsafe fn sub(self, count: usize) -> Selfwhere
T: Sized,
Subtracts an offset from a pointer (convenience for
.offset((count as isize).wrapping_neg())
).
count
is in units of T; e.g., a count
of 3 represents a pointer
offset of 3 * size_of::<T>()
bytes.
§Safety
If any of the following conditions are violated, the result is Undefined Behavior:
-
The computed offset,
count * size_of::<T>()
bytes, must not overflowisize
. -
If the computed offset is non-zero, then
self
must be derived from a pointer to some allocated object, and the entire memory range betweenself
and the result must be in bounds of that allocated object. In particular, this range must not “wrap around” the edge of the address space.
Allocated objects can never be larger than isize::MAX
bytes, so if the computed offset
stays in bounds of the allocated object, it is guaranteed to satisfy the first requirement.
This implies, for instance, that vec.as_ptr().add(vec.len())
(for vec: Vec<T>
) is always
safe.
§Examples
1.80.0 (const: 1.80.0) · Sourcepub const unsafe fn byte_sub(self, count: usize) -> Self
pub const unsafe fn byte_sub(self, count: usize) -> Self
Calculates the offset from a pointer in bytes (convenience for
.byte_offset((count as isize).wrapping_neg())
).
count
is in units of bytes.
This is purely a convenience for casting to a u8
pointer and
using sub
on it. See that method for documentation
and safety requirements.
For non-Sized
pointees this operation changes only the data pointer,
leaving the metadata untouched.
1.80.0 (const: 1.80.0) · Sourcepub const unsafe fn offset_from(self, origin: NonNull<T>) -> isizewhere
T: Sized,
pub const unsafe fn offset_from(self, origin: NonNull<T>) -> isizewhere
T: Sized,
Calculates the distance between two pointers within the same allocation. The returned value is in
units of T: the distance in bytes divided by mem::size_of::<T>()
.
This is equivalent to (self as isize - origin as isize) / (mem::size_of::<T>() as isize)
,
except that it has a lot more opportunities for UB, in exchange for the compiler
better understanding what you are doing.
The primary motivation of this method is for computing the len
of an array/slice
of T
that you are currently representing as a “start” and “end” pointer
(and “end” is “one past the end” of the array).
In that case, end.offset_from(start)
gets you the length of the array.
All of the following safety requirements are trivially satisfied for this usecase.
§Safety
If any of the following conditions are violated, the result is Undefined Behavior:
-
self
andorigin
must either- point to the same address, or
- both be derived from a pointer to the same allocated object, and the memory range between the two pointers must be in bounds of that object. (See below for an example.)
-
The distance between the pointers, in bytes, must be an exact multiple of the size of
T
.
As a consequence, the absolute distance between the pointers, in bytes, computed on
mathematical integers (without “wrapping around”), cannot overflow an isize
. This is
implied by the in-bounds requirement, and the fact that no allocated object can be larger
than isize::MAX
bytes.
The requirement for pointers to be derived from the same allocated object is primarily
needed for const
-compatibility: the distance between pointers into different allocated
objects is not known at compile-time. However, the requirement also exists at
runtime and may be exploited by optimizations. If you wish to compute the difference between
pointers that are not guaranteed to be from the same allocation, use (self as isize - origin as isize) / mem::size_of::<T>()
.
§Panics
This function panics if T
is a Zero-Sized Type (“ZST”).
§Examples
Basic usage:
use std::ptr::NonNull;
let a = [0; 5];
let ptr1: NonNull<u32> = NonNull::from(&a[1]);
let ptr2: NonNull<u32> = NonNull::from(&a[3]);
unsafe {
assert_eq!(ptr2.offset_from(ptr1), 2);
assert_eq!(ptr1.offset_from(ptr2), -2);
assert_eq!(ptr1.offset(2), ptr2);
assert_eq!(ptr2.offset(-2), ptr1);
}
Incorrect usage:
use std::ptr::NonNull;
let ptr1 = NonNull::new(Box::into_raw(Box::new(0u8))).unwrap();
let ptr2 = NonNull::new(Box::into_raw(Box::new(1u8))).unwrap();
let diff = (ptr2.addr().get() as isize).wrapping_sub(ptr1.addr().get() as isize);
// Make ptr2_other an "alias" of ptr2.add(1), but derived from ptr1.
let diff_plus_1 = diff.wrapping_add(1);
let ptr2_other = NonNull::new(ptr1.as_ptr().wrapping_byte_offset(diff_plus_1)).unwrap();
assert_eq!(ptr2.addr(), ptr2_other.addr());
// Since ptr2_other and ptr2 are derived from pointers to different objects,
// computing their offset is undefined behavior, even though
// they point to addresses that are in-bounds of the same object!
let one = unsafe { ptr2_other.offset_from(ptr2) }; // Undefined Behavior! ⚠️
1.80.0 (const: 1.80.0) · Sourcepub const unsafe fn byte_offset_from<U: ?Sized>(
self,
origin: NonNull<U>,
) -> isize
pub const unsafe fn byte_offset_from<U: ?Sized>( self, origin: NonNull<U>, ) -> isize
Calculates the distance between two pointers within the same allocation. The returned value is in units of bytes.
This is purely a convenience for casting to a u8
pointer and
using offset_from
on it. See that method for
documentation and safety requirements.
For non-Sized
pointees this operation considers only the data pointers,
ignoring the metadata.
Sourcepub const unsafe fn sub_ptr(self, subtracted: NonNull<T>) -> usizewhere
T: Sized,
🔬This is a nightly-only experimental API. (ptr_sub_ptr
#95892)
pub const unsafe fn sub_ptr(self, subtracted: NonNull<T>) -> usizewhere
T: Sized,
ptr_sub_ptr
#95892)Calculates the distance between two pointers within the same allocation, where it’s known that
self
is equal to or greater than origin
. The returned value is in
units of T: the distance in bytes is divided by mem::size_of::<T>()
.
This computes the same value that offset_from
would compute, but with the added precondition that the offset is
guaranteed to be non-negative. This method is equivalent to
usize::try_from(self.offset_from(origin)).unwrap_unchecked()
,
but it provides slightly more information to the optimizer, which can
sometimes allow it to optimize slightly better with some backends.
This method can be though of as recovering the count
that was passed
to add
(or, with the parameters in the other order,
to sub
). The following are all equivalent, assuming
that their safety preconditions are met:
§Safety
-
The distance between the pointers must be non-negative (
self >= origin
) -
All the safety conditions of
offset_from
apply to this method as well; see it for the full details.
Importantly, despite the return type of this method being able to represent
a larger offset, it’s still not permitted to pass pointers which differ
by more than isize::MAX
bytes. As such, the result of this method will
always be less than or equal to isize::MAX as usize
.
§Panics
This function panics if T
is a Zero-Sized Type (“ZST”).
§Examples
#![feature(ptr_sub_ptr)]
use std::ptr::NonNull;
let a = [0; 5];
let ptr1: NonNull<u32> = NonNull::from(&a[1]);
let ptr2: NonNull<u32> = NonNull::from(&a[3]);
unsafe {
assert_eq!(ptr2.sub_ptr(ptr1), 2);
assert_eq!(ptr1.add(2), ptr2);
assert_eq!(ptr2.sub(2), ptr1);
assert_eq!(ptr2.sub_ptr(ptr2), 0);
}
// This would be incorrect, as the pointers are not correctly ordered:
// ptr1.sub_ptr(ptr2)
Sourcepub const unsafe fn byte_sub_ptr<U: ?Sized>(self, origin: NonNull<U>) -> usize
🔬This is a nightly-only experimental API. (ptr_sub_ptr
#95892)
pub const unsafe fn byte_sub_ptr<U: ?Sized>(self, origin: NonNull<U>) -> usize
ptr_sub_ptr
#95892)Calculates the distance between two pointers within the same allocation, where it’s known that
self
is equal to or greater than origin
. The returned value is in
units of bytes.
This is purely a convenience for casting to a u8
pointer and
using sub_ptr
on it. See that method for
documentation and safety requirements.
For non-Sized
pointees this operation considers only the data pointers,
ignoring the metadata.
1.80.0 (const: 1.80.0) · Sourcepub const unsafe fn read(self) -> Twhere
T: Sized,
pub const unsafe fn read(self) -> Twhere
T: Sized,
Reads the value from self
without moving it. This leaves the
memory in self
unchanged.
See ptr::read
for safety concerns and examples.
1.80.0 · Sourcepub unsafe fn read_volatile(self) -> Twhere
T: Sized,
pub unsafe fn read_volatile(self) -> Twhere
T: Sized,
Performs a volatile read of the value from self
without moving it. This
leaves the memory in self
unchanged.
Volatile operations are intended to act on I/O memory, and are guaranteed to not be elided or reordered by the compiler across other volatile operations.
See ptr::read_volatile
for safety concerns and examples.
1.80.0 (const: 1.80.0) · Sourcepub const unsafe fn read_unaligned(self) -> Twhere
T: Sized,
pub const unsafe fn read_unaligned(self) -> Twhere
T: Sized,
Reads the value from self
without moving it. This leaves the
memory in self
unchanged.
Unlike read
, the pointer may be unaligned.
See ptr::read_unaligned
for safety concerns and examples.
1.80.0 (const: 1.83.0) · Sourcepub const unsafe fn copy_to(self, dest: NonNull<T>, count: usize)where
T: Sized,
pub const unsafe fn copy_to(self, dest: NonNull<T>, count: usize)where
T: Sized,
1.80.0 (const: 1.83.0) · Sourcepub const unsafe fn copy_to_nonoverlapping(self, dest: NonNull<T>, count: usize)where
T: Sized,
pub const unsafe fn copy_to_nonoverlapping(self, dest: NonNull<T>, count: usize)where
T: Sized,
Copies count * size_of<T>
bytes from self
to dest
. The source
and destination may not overlap.
NOTE: this has the same argument order as ptr::copy_nonoverlapping
.
See ptr::copy_nonoverlapping
for safety concerns and examples.
1.80.0 (const: 1.83.0) · Sourcepub const unsafe fn copy_from(self, src: NonNull<T>, count: usize)where
T: Sized,
pub const unsafe fn copy_from(self, src: NonNull<T>, count: usize)where
T: Sized,
1.80.0 (const: 1.83.0) · Sourcepub const unsafe fn copy_from_nonoverlapping(
self,
src: NonNull<T>,
count: usize,
)where
T: Sized,
pub const unsafe fn copy_from_nonoverlapping(
self,
src: NonNull<T>,
count: usize,
)where
T: Sized,
Copies count * size_of<T>
bytes from src
to self
. The source
and destination may not overlap.
NOTE: this has the opposite argument order of ptr::copy_nonoverlapping
.
See ptr::copy_nonoverlapping
for safety concerns and examples.
1.80.0 · Sourcepub unsafe fn drop_in_place(self)
pub unsafe fn drop_in_place(self)
Executes the destructor (if any) of the pointed-to value.
See ptr::drop_in_place
for safety concerns and examples.
1.80.0 (const: 1.83.0) · Sourcepub const unsafe fn write(self, val: T)where
T: Sized,
pub const unsafe fn write(self, val: T)where
T: Sized,
Overwrites a memory location with the given value without reading or dropping the old value.
See ptr::write
for safety concerns and examples.
1.80.0 (const: 1.83.0) · Sourcepub const unsafe fn write_bytes(self, val: u8, count: usize)where
T: Sized,
pub const unsafe fn write_bytes(self, val: u8, count: usize)where
T: Sized,
Invokes memset on the specified pointer, setting count * size_of::<T>()
bytes of memory starting at self
to val
.
See ptr::write_bytes
for safety concerns and examples.
1.80.0 · Sourcepub unsafe fn write_volatile(self, val: T)where
T: Sized,
pub unsafe fn write_volatile(self, val: T)where
T: Sized,
Performs a volatile write of a memory location with the given value without reading or dropping the old value.
Volatile operations are intended to act on I/O memory, and are guaranteed to not be elided or reordered by the compiler across other volatile operations.
See ptr::write_volatile
for safety concerns and examples.
1.80.0 (const: 1.83.0) · Sourcepub const unsafe fn write_unaligned(self, val: T)where
T: Sized,
pub const unsafe fn write_unaligned(self, val: T)where
T: Sized,
Overwrites a memory location with the given value without reading or dropping the old value.
Unlike write
, the pointer may be unaligned.
See ptr::write_unaligned
for safety concerns and examples.
1.80.0 · Sourcepub unsafe fn replace(self, src: T) -> Twhere
T: Sized,
pub unsafe fn replace(self, src: T) -> Twhere
T: Sized,
Replaces the value at self
with src
, returning the old
value, without dropping either.
See ptr::replace
for safety concerns and examples.
1.80.0 (const: unstable) · Sourcepub unsafe fn swap(self, with: NonNull<T>)where
T: Sized,
pub unsafe fn swap(self, with: NonNull<T>)where
T: Sized,
Swaps the values at two mutable locations of the same type, without
deinitializing either. They may overlap, unlike mem::swap
which is
otherwise equivalent.
See ptr::swap
for safety concerns and examples.
1.80.0 · Sourcepub fn align_offset(self, align: usize) -> usizewhere
T: Sized,
pub fn align_offset(self, align: usize) -> usizewhere
T: Sized,
Computes the offset that needs to be applied to the pointer in order to make it aligned to
align
.
If it is not possible to align the pointer, the implementation returns
usize::MAX
.
The offset is expressed in number of T
elements, and not bytes.
There are no guarantees whatsoever that offsetting the pointer will not overflow or go beyond the allocation that the pointer points into. It is up to the caller to ensure that the returned offset is correct in all terms other than alignment.
When this is called during compile-time evaluation (which is unstable), the implementation
may return usize::MAX
in cases where that can never happen at runtime. This is because the
actual alignment of pointers is not known yet during compile-time, so an offset with
guaranteed alignment can sometimes not be computed. For example, a buffer declared as [u8; N]
might be allocated at an odd or an even address, but at compile-time this is not yet
known, so the execution has to be correct for either choice. It is therefore impossible to
find an offset that is guaranteed to be 2-aligned. (This behavior is subject to change, as usual
for unstable APIs.)
§Panics
The function panics if align
is not a power-of-two.
§Examples
Accessing adjacent u8
as u16
use std::mem::align_of;
use std::ptr::NonNull;
let x = [5_u8, 6, 7, 8, 9];
let ptr = NonNull::new(x.as_ptr() as *mut u8).unwrap();
let offset = ptr.align_offset(align_of::<u16>());
if offset < x.len() - 1 {
let u16_ptr = ptr.add(offset).cast::<u16>();
assert!(u16_ptr.read() == u16::from_ne_bytes([5, 6]) || u16_ptr.read() == u16::from_ne_bytes([6, 7]));
} else {
// while the pointer can be aligned via `offset`, it would point
// outside the allocation
}
1.79.0 · Sourcepub fn is_aligned(self) -> boolwhere
T: Sized,
pub fn is_aligned(self) -> boolwhere
T: Sized,
Returns whether the pointer is properly aligned for T
.
§Examples
use std::ptr::NonNull;
// On some platforms, the alignment of i32 is less than 4.
#[repr(align(4))]
struct AlignedI32(i32);
let data = AlignedI32(42);
let ptr = NonNull::<AlignedI32>::from(&data);
assert!(ptr.is_aligned());
assert!(!NonNull::new(ptr.as_ptr().wrapping_byte_add(1)).unwrap().is_aligned());
Sourcepub fn is_aligned_to(self, align: usize) -> bool
🔬This is a nightly-only experimental API. (pointer_is_aligned_to
#96284)
pub fn is_aligned_to(self, align: usize) -> bool
pointer_is_aligned_to
#96284)Returns whether the pointer is aligned to align
.
For non-Sized
pointees this operation considers only the data pointer,
ignoring the metadata.
§Panics
The function panics if align
is not a power-of-two (this includes 0).
§Examples
#![feature(pointer_is_aligned_to)]
// On some platforms, the alignment of i32 is less than 4.
#[repr(align(4))]
struct AlignedI32(i32);
let data = AlignedI32(42);
let ptr = &data as *const AlignedI32;
assert!(ptr.is_aligned_to(1));
assert!(ptr.is_aligned_to(2));
assert!(ptr.is_aligned_to(4));
assert!(ptr.wrapping_byte_add(2).is_aligned_to(2));
assert!(!ptr.wrapping_byte_add(2).is_aligned_to(4));
assert_ne!(ptr.is_aligned_to(8), ptr.wrapping_add(1).is_aligned_to(8));
Source§impl<T> NonNull<[T]>
impl<T> NonNull<[T]>
1.70.0 (const: 1.83.0) · Sourcepub const fn slice_from_raw_parts(data: NonNull<T>, len: usize) -> Self
pub const fn slice_from_raw_parts(data: NonNull<T>, len: usize) -> Self
Creates a non-null raw slice from a thin pointer and a length.
The len
argument is the number of elements, not the number of bytes.
This function is safe, but dereferencing the return value is unsafe.
See the documentation of slice::from_raw_parts
for slice safety requirements.
§Examples
use std::ptr::NonNull;
// create a slice pointer when starting out with a pointer to the first element
let mut x = [5, 6, 7];
let nonnull_pointer = NonNull::new(x.as_mut_ptr()).unwrap();
let slice = NonNull::slice_from_raw_parts(nonnull_pointer, 3);
assert_eq!(unsafe { slice.as_ref()[2] }, 7);
(Note that this example artificially demonstrates a use of this method,
but let slice = NonNull::from(&x[..]);
would be a better way to write code like this.)
1.63.0 (const: 1.63.0) · Sourcepub const fn len(self) -> usize
pub const fn len(self) -> usize
Returns the length of a non-null raw slice.
The returned value is the number of elements, not the number of bytes.
This function is safe, even when the non-null raw slice cannot be dereferenced to a slice because the pointer does not have a valid address.
§Examples
1.79.0 (const: 1.79.0) · Sourcepub const fn is_empty(self) -> bool
pub const fn is_empty(self) -> bool
Returns true
if the non-null raw slice has a length of 0.
§Examples
Sourcepub const fn as_non_null_ptr(self) -> NonNull<T>
🔬This is a nightly-only experimental API. (slice_ptr_get
#74265)
pub const fn as_non_null_ptr(self) -> NonNull<T>
slice_ptr_get
#74265)Returns a non-null pointer to the slice’s buffer.
§Examples
Sourcepub const fn as_mut_ptr(self) -> *mut T
🔬This is a nightly-only experimental API. (slice_ptr_get
#74265)
pub const fn as_mut_ptr(self) -> *mut T
slice_ptr_get
#74265)Returns a raw pointer to the slice’s buffer.
§Examples
Sourcepub const unsafe fn as_uninit_slice<'a>(self) -> &'a [MaybeUninit<T>]
🔬This is a nightly-only experimental API. (ptr_as_uninit
#75402)
pub const unsafe fn as_uninit_slice<'a>(self) -> &'a [MaybeUninit<T>]
ptr_as_uninit
#75402)Returns a shared reference to a slice of possibly uninitialized values. In contrast to
as_ref
, this does not require that the value has to be initialized.
For the mutable counterpart see as_uninit_slice_mut
.
§Safety
When calling this method, you have to ensure that all of the following is true:
-
The pointer must be valid for reads for
ptr.len() * mem::size_of::<T>()
many bytes, and it must be properly aligned. This means in particular:-
The entire memory range of this slice must be contained within a single allocated object! Slices can never span across multiple allocated objects.
-
The pointer must be aligned even for zero-length slices. One reason for this is that enum layout optimizations may rely on references (including slices of any length) being aligned and non-null to distinguish them from other data. You can obtain a pointer that is usable as
data
for zero-length slices usingNonNull::dangling()
.
-
-
The total size
ptr.len() * mem::size_of::<T>()
of the slice must be no larger thanisize::MAX
. See the safety documentation ofpointer::offset
. -
You must enforce Rust’s aliasing rules, since the returned lifetime
'a
is arbitrarily chosen and does not necessarily reflect the actual lifetime of the data. In particular, while this reference exists, the memory the pointer points to must not get mutated (except insideUnsafeCell
).
This applies even if the result of this method is unused!
See also slice::from_raw_parts
.
Sourcepub const unsafe fn as_uninit_slice_mut<'a>(self) -> &'a mut [MaybeUninit<T>]
🔬This is a nightly-only experimental API. (ptr_as_uninit
#75402)
pub const unsafe fn as_uninit_slice_mut<'a>(self) -> &'a mut [MaybeUninit<T>]
ptr_as_uninit
#75402)Returns a unique reference to a slice of possibly uninitialized values. In contrast to
as_mut
, this does not require that the value has to be initialized.
For the shared counterpart see as_uninit_slice
.
§Safety
When calling this method, you have to ensure that all of the following is true:
-
The pointer must be valid for reads and writes for
ptr.len() * mem::size_of::<T>()
many bytes, and it must be properly aligned. This means in particular:-
The entire memory range of this slice must be contained within a single allocated object! Slices can never span across multiple allocated objects.
-
The pointer must be aligned even for zero-length slices. One reason for this is that enum layout optimizations may rely on references (including slices of any length) being aligned and non-null to distinguish them from other data. You can obtain a pointer that is usable as
data
for zero-length slices usingNonNull::dangling()
.
-
-
The total size
ptr.len() * mem::size_of::<T>()
of the slice must be no larger thanisize::MAX
. See the safety documentation ofpointer::offset
. -
You must enforce Rust’s aliasing rules, since the returned lifetime
'a
is arbitrarily chosen and does not necessarily reflect the actual lifetime of the data. In particular, while this reference exists, the memory the pointer points to must not get accessed (read or written) through any other pointer.
This applies even if the result of this method is unused!
See also slice::from_raw_parts_mut
.
§Examples
#![feature(allocator_api, ptr_as_uninit)]
use std::alloc::{Allocator, Layout, Global};
use std::mem::MaybeUninit;
use std::ptr::NonNull;
let memory: NonNull<[u8]> = Global.allocate(Layout::new::<[u8; 32]>())?;
// This is safe as `memory` is valid for reads and writes for `memory.len()` many bytes.
// Note that calling `memory.as_mut()` is not allowed here as the content may be uninitialized.
let slice: &mut [MaybeUninit<u8>] = unsafe { memory.as_uninit_slice_mut() };
Sourcepub unsafe fn get_unchecked_mut<I>(self, index: I) -> NonNull<I::Output>where
I: SliceIndex<[T]>,
🔬This is a nightly-only experimental API. (slice_ptr_get
#74265)
pub unsafe fn get_unchecked_mut<I>(self, index: I) -> NonNull<I::Output>where
I: SliceIndex<[T]>,
slice_ptr_get
#74265)Returns a raw pointer to an element or subslice, without doing bounds checking.
Calling this method with an out-of-bounds index or when self
is not dereferenceable
is undefined behavior even if the resulting pointer is not used.
§Examples
Trait Implementations§
1.25.0 · Source§impl<T: ?Sized> Ord for NonNull<T>
impl<T: ?Sized> Ord for NonNull<T>
1.25.0 · Source§impl<T: ?Sized> PartialOrd for NonNull<T>
impl<T: ?Sized> PartialOrd for NonNull<T>
impl<T, U: ?Sized> CoerceUnsized<NonNull<U>> for NonNull<T>
impl<T: ?Sized> Copy for NonNull<T>
impl<T, U: ?Sized> DispatchFromDyn<NonNull<U>> for NonNull<T>
impl<T: ?Sized> Eq for NonNull<T>
impl<T: ?Sized> PinCoerceUnsized for NonNull<T>
impl<T: ?Sized> !Send for NonNull<T>
NonNull
pointers are not Send
because the data they reference may be aliased.
impl<T: ?Sized> !Sync for NonNull<T>
NonNull
pointers are not Sync
because the data they reference may be aliased.