pub unsafe auto trait Send { }Expand description
Types that can be transferred across thread boundaries.
This trait is automatically implemented when the compiler determines it’s appropriate.
An example of a non-Send type is the reference-counting pointer
rc::Rc. If two threads attempt to clone Rcs that point to the same
reference-counted value, they might try to update the reference count at the
same time, which is undefined behavior because Rc doesn’t use atomic
operations. Its cousin sync::Arc does use atomic operations (incurring
some overhead) and thus is Send.
See the Nomicon and the Sync trait for more details.
Dyn Compatibility§
This trait is dyn compatible.
In older versions of Rust, dyn compatibility was called "object safety".
Implementors§
impl !Send for Arguments<'_>
impl !Send for LocalWaker
impl Send for core::ffi::c_str::Bytes<'_>
impl Send for Custom
impl Send for CustomOwner
impl Send for Location<'_>
impl Send for Repr
impl Send for ResumeTy
impl Send for TypeId
impl Send for Waker
impl<'a> Send for core::io::io_slice::IoSlice<'a>
impl<'a> Send for core::io::io_slice::IoSliceMut<'a>
impl<Dyn: PointeeSized> Send for DynMetadata<Dyn>
impl<T: AtomicPrimitive> Send for Atomic<T>
impl<T: PointeeSized> !Send for *const T
impl<T: PointeeSized> !Send for *mut T
impl<T: PointeeSized> !Send for NonNull<T>
NonNull pointers are not Send because the data they reference may be aliased.
impl<T: Send + PointeeSized> Send for Unique<T>
Unique pointers are Send if T is Send because the data they
reference is unaliased. Note that this aliasing invariant is
unenforced by the type system; the abstraction using the
Unique must enforce it.