Struct safer_ffi::ptr::NonNullOwned
source · [−]#[repr(transparent)]pub struct NonNullOwned<T>(pub NonNull<T>, pub PhantomData<T>);
Tuple Fields
0: NonNull<T>
1: PhantomData<T>
Implementations
sourceimpl<T> NonNullOwned<T>
impl<T> NonNullOwned<T>
pub fn as_ptr(&self) -> *const T
pub fn cast<U>(self: NonNullOwned<T>) -> NonNullOwned<U>
sourceimpl<T> NonNullOwned<T>
impl<T> NonNullOwned<T>
pub fn as_mut_ptr(&mut self) -> *mut T
pub fn copy(self: &mut NonNullOwned<T>) -> NonNullOwned<T>
sourceimpl<__> NonNullOwned<__>
impl<__> NonNullOwned<__>
pub unsafe fn dealloc<T>(self)
alloc
only.pub unsafe fn drop_in_place_and_dealloc<T>(self)
alloc
only.pub unsafe fn drop_in_place<T>(self)
Methods from Deref<Target = NonNull<T>>
sourcepub unsafe fn as_uninit_ref<'a>(&self) -> &'a MaybeUninit<T>
🔬 This is a nightly-only experimental API. (ptr_as_uninit
)
pub unsafe fn as_uninit_ref<'a>(&self) -> &'a MaybeUninit<T>
ptr_as_uninit
)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 all of the following is true:
-
The pointer must be properly aligned.
-
It must be “dereferenceable” in the sense defined in the module documentation.
-
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!
sourcepub unsafe fn as_uninit_mut<'a>(&mut self) -> &'a mut MaybeUninit<T>
🔬 This is a nightly-only experimental API. (ptr_as_uninit
)
pub unsafe fn as_uninit_mut<'a>(&mut self) -> &'a mut MaybeUninit<T>
ptr_as_uninit
)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 all of the following is true:
-
The pointer must be properly aligned.
-
It must be “dereferenceable” in the sense defined in the module documentation.
-
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!
1.25.0 · sourcepub unsafe fn as_ref<'a>(&self) -> &'a T
pub 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 all of the following is true:
-
The pointer must be properly aligned.
-
It must be “dereferenceable” in the sense defined in the module documentation.
-
The pointer must point to an initialized instance of
T
. -
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! (The part about being initialized is not yet fully decided, but until it is, the only safe approach is to ensure that they are indeed initialized.)
Examples
use std::ptr::NonNull;
let mut x = 0u32;
let ptr = NonNull::new(&mut x as *mut _).expect("ptr is null!");
let ref_x = unsafe { ptr.as_ref() };
println!("{ref_x}");
1.25.0 · sourcepub unsafe fn as_mut<'a>(&mut self) -> &'a mut T
pub 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 all of the following is true:
-
The pointer must be properly aligned.
-
It must be “dereferenceable” in the sense defined in the module documentation.
-
The pointer must point to an initialized instance of
T
. -
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! (The part about being initialized is not yet fully decided, but until it is, the only safe approach is to ensure that they are indeed initialized.)
Examples
use std::ptr::NonNull;
let mut x = 0u32;
let mut ptr = NonNull::new(&mut x).expect("null pointer");
let x_ref = unsafe { ptr.as_mut() };
assert_eq!(*x_ref, 0);
*x_ref += 2;
assert_eq!(*x_ref, 2);
sourcepub unsafe fn as_uninit_slice<'a>(&self) -> &'a [MaybeUninit<T>]
🔬 This is a nightly-only experimental API. (ptr_as_uninit
)
pub unsafe fn as_uninit_slice<'a>(&self) -> &'a [MaybeUninit<T>]
ptr_as_uninit
)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 unsafe fn as_uninit_slice_mut<'a>(&self) -> &'a mut [MaybeUninit<T>]
🔬 This is a nightly-only experimental API. (ptr_as_uninit
)
pub unsafe fn as_uninit_slice_mut<'a>(&self) -> &'a mut [MaybeUninit<T>]
ptr_as_uninit
)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() };
Trait Implementations
sourceimpl<T> Debug for NonNullOwned<T>
impl<T> Debug for NonNullOwned<T>
sourceimpl<T> Deref for NonNullOwned<T>
impl<T> Deref for NonNullOwned<T>
sourceimpl<T> DerefMut for NonNullOwned<T>
impl<T> DerefMut for NonNullOwned<T>
sourcefn deref_mut(self: &mut NonNullOwned<T>) -> &mut NonNull<T>
fn deref_mut(self: &mut NonNullOwned<T>) -> &mut NonNull<T>
Mutably dereferences the value.
sourceimpl<T> From<NonNull<T>> for NonNullOwned<T>
impl<T> From<NonNull<T>> for NonNullOwned<T>
Auto Trait Implementations
impl<T> RefUnwindSafe for NonNullOwned<T> where
T: RefUnwindSafe,
impl<T> !Send for NonNullOwned<T>
impl<T> !Sync for NonNullOwned<T>
impl<T> Unpin for NonNullOwned<T> where
T: Unpin,
impl<T> UnwindSafe for NonNullOwned<T> where
T: UnwindSafe + RefUnwindSafe,
Blanket Implementations
sourceimpl<T> BorrowMut<T> for T where
T: ?Sized,
impl<T> BorrowMut<T> for T where
T: ?Sized,
const: unstable · sourcefn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Mutably borrows from an owned value. Read more