pub unsafe auto trait Sync { }Expand description
Types for which it is safe to share references between threads.
This trait is automatically implemented when the compiler determines it’s appropriate.
The precise definition is: a type T is Sync if and only if &T is
Send. In other words, if there is no possibility of
undefined behavior (including data races) when passing
&T references between threads.
As one would expect, primitive types like u8 and f64
are all Sync, and so are simple aggregate types containing them,
like tuples, structs and enums. More examples of basic Sync
types include “immutable” types like &T, and those with simple
inherited mutability, such as Box<T>, Vec<T> and
most other collection types. (Generic parameters need to be Sync
for their container to be Sync.)
A somewhat surprising consequence of the definition is that &mut T
is Sync (if T is Sync) even though it seems like that might
provide unsynchronized mutation. The trick is that a mutable
reference behind a shared reference (that is, & &mut T)
becomes read-only, as if it were a & &T. Hence there is no risk
of a data race.
A shorter overview of how Sync and Send relate to referencing:
&TisSendif and only ifTisSync&mut TisSendif and only ifTisSend&Tand&mut TareSyncif and only ifTisSync
Types that are not Sync are those that have “interior
mutability” in a non-thread-safe form, such as Cell
and RefCell. These types allow for mutation of
their contents even through an immutable, shared reference. For
example the set method on Cell<T> takes &self, so it requires
only a shared reference &Cell<T>. The method performs no
synchronization, thus Cell cannot be Sync.
Another example of a non-Sync type is the reference-counting
pointer Rc. Given any reference &Rc<T>, you can clone
a new Rc<T>, modifying the reference counts in a non-atomic way.
For cases when one does need thread-safe interior mutability,
Rust provides atomic data types, as well as explicit locking via
sync::Mutex and sync::RwLock. These types
ensure that any mutation cannot cause data races, hence the types
are Sync. Likewise, sync::Arc provides a thread-safe
analogue of Rc.
Any types with interior mutability must also use the
cell::UnsafeCell wrapper around the value(s) which
can be mutated through a shared reference. Failing to doing this is
undefined behavior. For example, transmute-ing
from &T to &mut T is invalid.
See the Nomicon for more details about Sync.
Dyn Compatibility§
This trait is dyn compatible.
In older versions of Rust, dyn compatibility was called "object safety".
Implementors§
impl !Sync for Arguments<'_>
impl !Sync for LocalWaker
impl Sync for core::ffi::c_str::Bytes<'_>
impl Sync for Custom
impl Sync for CustomOwner
impl Sync for Location<'_>
impl Sync for Repr
impl Sync for ResumeTy
impl Sync for TypeId
impl Sync for Waker
impl<'a> Sync for core::io::io_slice::IoSlice<'a>
impl<'a> Sync for core::io::io_slice::IoSliceMut<'a>
impl<Dyn: PointeeSized> Sync for DynMetadata<Dyn>
impl<T: ?Sized + Sync> Sync for SyncUnsafeCell<T>
impl<T: ?Sized + Sync> Sync for UnsafePinned<T>
impl<T: ?Sized> !Sync for Cell<T>
impl<T: ?Sized> !Sync for RefCell<T>
impl<T: ?Sized> !Sync for UnsafeCell<T>
impl<T: ?Sized> Sync for SyncView<T>
impl<T: AtomicPrimitive> Sync for Atomic<T>
impl<T: PointeeSized> !Sync for *const T
impl<T: PointeeSized> !Sync for *mut T
impl<T: PointeeSized> !Sync for NonNull<T>
NonNull pointers are not Sync because the data they reference may be aliased.
impl<T: Sync + PointeeSized> Sync for Unique<T>
Unique pointers are Sync if T is Sync 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.