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.
Implementors§
impl !Send for TokenTree
impl !Send for Arguments<'_>
impl !Send for LocalWaker
impl !Send for ExpandError
impl !Send for Group
impl !Send for LexError
impl !Send for Punct
impl !Send for Span
impl !Send for TokenStream
impl !Send for Args
impl !Send for ArgsOs
impl Send for scrypto_test::prelude::rust::string::Drain<'_>
impl Send for TypeId
impl Send for core::ffi::c_str::Bytes<'_>
impl Send for core::panic::location::Location<'_>
impl Send for Waker
impl Send for Select<'_>
impl Send for Collector
impl Send for Parker
impl Send for Unparker
impl<'a> Send for IoSlice<'a>
impl<'a> Send for IoSliceMut<'a>
impl<'a, 'b, K, Q, V, S, A> Send for OccupiedEntryRef<'a, 'b, K, Q, V, S, A>
impl<'a, 'i, K, V> Send for moka::sync_base::iter::Iter<'i, K, V>
impl<'a, R, T> Send for lock_api::mutex::MappedMutexGuard<'a, R, T>
impl<'a, R, T> Send for lock_api::rwlock::MappedRwLockReadGuard<'a, R, T>
impl<'a, R, T> Send for lock_api::rwlock::MappedRwLockWriteGuard<'a, R, T>
impl<'a, T> Send for smallvec::Drain<'a, T>
impl<'a, T> Send for ArcBorrow<'a, T>
impl<'a, T, const CAP: usize> Send for arrayvec::arrayvec::Drain<'a, T, CAP>where
T: Send,
impl<A> Send for SmallVec<A>
impl<A, B> Send for ArcUnion<A, B>
impl<C> Send for Secp256k1<C>where
C: Context,
impl<Dyn> Send for DynMetadata<Dyn>where
Dyn: ?Sized,
impl<H, T> Send for ThinArc<H, T>
impl<Idx, T> Send for ComponentVec<Idx, T>where
T: Send,
ComponentVec does not store Idx therefore it is Send without its bound.
impl<Idx, T> Send for Arena<Idx, T>where
T: Send,
Arena does not store Idx therefore it is Send without its bound.
impl<K, V> Send for hashbrown::map::IterMut<'_, K, V>
impl<K, V> Send for hashbrown::map::IterMut<'_, K, V>
impl<K, V, S> Send for Cache<K, V, S>
impl<K, V, S> Send for SegmentedCache<K, V, S>
impl<K, V, S, A> Send for hashbrown::map::OccupiedEntry<'_, K, V, S, A>
impl<K, V, S, A> Send for hashbrown::map::OccupiedEntry<'_, K, V, S, A>
impl<K, V, S, A> Send for hashbrown::map::RawOccupiedEntryMut<'_, K, V, S, A>
impl<R, G> Send for RawReentrantMutex<R, G>
impl<R, G, T> Send for ReentrantMutex<R, G, T>
impl<R, T> Send for lock_api::mutex::Mutex<R, T>
impl<R, T> Send for lock_api::rwlock::RwLock<R, T>
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 scrypto_test::prelude::rust::sync::nonpoison::MappedMutexGuard<'_, T>where
T: ?Sized,
impl<T> !Send for scrypto_test::prelude::rust::sync::nonpoison::MappedRwLockReadGuard<'_, T>where
T: ?Sized,
impl<T> !Send for scrypto_test::prelude::rust::sync::nonpoison::MappedRwLockWriteGuard<'_, T>where
T: ?Sized,
impl<T> !Send for scrypto_test::prelude::rust::sync::nonpoison::MutexGuard<'_, T>where
T: ?Sized,
A MutexGuard is not Send to maximize platform portability.
On platforms that use POSIX threads (commonly referred to as pthreads) there is a requirement to
release mutex locks on the same thread they were acquired.
For this reason, MutexGuard must not implement Send to prevent it being dropped from
another thread.
impl<T> !Send for scrypto_test::prelude::rust::sync::nonpoison::RwLockReadGuard<'_, T>where
T: ?Sized,
impl<T> !Send for scrypto_test::prelude::rust::sync::nonpoison::RwLockWriteGuard<'_, T>where
T: ?Sized,
impl<T> !Send for scrypto_test::prelude::rust::sync::MappedMutexGuard<'_, T>where
T: ?Sized,
impl<T> !Send for scrypto_test::prelude::rust::sync::MappedRwLockReadGuard<'_, T>where
T: ?Sized,
impl<T> !Send for scrypto_test::prelude::rust::sync::MappedRwLockWriteGuard<'_, T>where
T: ?Sized,
impl<T> !Send for scrypto_test::prelude::rust::sync::MutexGuard<'_, T>where
T: ?Sized,
A MutexGuard is not Send to maximize platform portability.
On platforms that use POSIX threads (commonly referred to as pthreads) there is a requirement to
release mutex locks on the same thread they were acquired.
For this reason, MutexGuard must not implement Send to prevent it being dropped from
another thread.
impl<T> !Send for ReentrantLockGuard<'_, T>where
T: ?Sized,
impl<T> !Send for scrypto_test::prelude::rust::sync::RwLockReadGuard<'_, T>where
T: ?Sized,
impl<T> !Send for scrypto_test::prelude::rust::sync::RwLockWriteGuard<'_, T>where
T: ?Sized,
impl<T> Send for &T
impl<T> Send for Cell<T>
impl<T> Send for RefCell<T>
impl<T> Send for ThinBox<T>
ThinBox<T> is Send if T is Send because the data is owned.
impl<T> Send for NonZero<T>where
T: ZeroablePrimitive + Send,
impl<T> Send for ChunksExactMut<'_, T>where
T: Send,
impl<T> Send for ChunksMut<'_, T>where
T: Send,
impl<T> Send for scrypto_test::prelude::rust::slice::Iter<'_, T>where
T: Sync,
impl<T> Send for scrypto_test::prelude::rust::slice::IterMut<'_, T>where
T: Send,
impl<T> Send for RChunksExactMut<'_, T>where
T: Send,
impl<T> Send for RChunksMut<'_, T>where
T: Send,
impl<T> Send for AtomicPtr<T>
impl<T> Send for scrypto_test::prelude::rust::sync::mpmc::Receiver<T>where
T: Send,
impl<T> Send for scrypto_test::prelude::rust::sync::mpmc::Sender<T>where
T: Send,
impl<T> Send for scrypto_test::prelude::rust::sync::mpsc::Receiver<T>where
T: Send,
impl<T> Send for scrypto_test::prelude::rust::sync::mpsc::Sender<T>where
T: Send,
impl<T> Send for SyncSender<T>where
T: Send,
impl<T> Send for scrypto_test::prelude::rust::sync::nonpoison::Mutex<T>
T must be Send for a Mutex to be Send because it is possible to acquire
the owned T from the Mutex via into_inner.
impl<T> Send for scrypto_test::prelude::rust::sync::nonpoison::RwLock<T>
impl<T> Send for scrypto_test::prelude::rust::sync::Mutex<T>
T must be Send for a Mutex to be Send because it is possible to acquire
the owned T from the Mutex via into_inner.