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 for more details.
Implementors§
impl !Send for Args
impl !Send for ArgsOs
impl Send for alloc::string::Drain<'_>
impl Send for Waker
impl<'a> Send for IoSlice<'a>
impl<'a> Send for IoSliceMut<'a>
impl<Dyn> Send for DynMetadata<Dyn>where Dyn: ?Sized,
impl<T> !Send for *const Twhere T: ?Sized,
impl<T> !Send for *mut Twhere T: ?Sized,
impl<T> !Send for NonNull<T>where T: ?Sized,
NonNull pointers are not Send because the data they reference may be aliased.
impl<T> !Send for Rc<T>where T: ?Sized,
impl<T> !Send for sp_std::rc::Weak<T>where T: ?Sized,
impl<T> !Send for MutexGuard<'_, T>where T: ?Sized,
impl<T> !Send for RwLockReadGuard<'_, T>where T: ?Sized,
impl<T> !Send for RwLockWriteGuard<'_, T>where T: ?Sized,
impl<T> Send for &Twhere T: Sync + ?Sized,
impl<T> Send for ThinBox<T>where T: Send + ?Sized,
ThinBox<T> is Send if T is Send because the data is owned.