mirror of
https://github.com/rust-lang/rust.git
synced 2024-11-25 16:24:46 +00:00
Rollup merge of #111065 - est31:send_mut_ref, r=m-ou-se
Explicitly document how Send and Sync relate to references Some of these relations were already mentioned in the text, but that Send is implemented for &mut impl Send was not mentioned, neither did the docs list when &T is Sync. Inspired by the discussion in #110961. [Proof](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=ed77bfc3c77ba664400ebc2734f500e6) based on `@lukas-code` 's [example](https://github.com/rust-lang/rust/pull/110961#discussion_r1181220662).
This commit is contained in:
commit
15eebac9d9
@ -24,7 +24,7 @@ use crate::hash::Hasher;
|
||||
/// operations. Its cousin [`sync::Arc`][arc] does use atomic operations (incurring
|
||||
/// some overhead) and thus is `Send`.
|
||||
///
|
||||
/// See [the Nomicon](../../nomicon/send-and-sync.html) for more details.
|
||||
/// See [the Nomicon](../../nomicon/send-and-sync.html) and the [`Sync`] trait for more details.
|
||||
///
|
||||
/// [`Rc`]: ../../std/rc/struct.Rc.html
|
||||
/// [arc]: ../../std/sync/struct.Arc.html
|
||||
@ -426,6 +426,11 @@ pub macro Copy($item:item) {
|
||||
/// 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:
|
||||
/// * `&T` is [`Send`] if and only if `T` is [`Sync`]
|
||||
/// * `&mut T` is [`Send`] if and only if `T` is [`Send`]
|
||||
/// * `&T` and `&mut T` are [`Sync`] if and only if `T` is [`Sync`]
|
||||
///
|
||||
/// Types that are not `Sync` are those that have "interior
|
||||
/// mutability" in a non-thread-safe form, such as [`Cell`][cell]
|
||||
/// and [`RefCell`][refcell]. These types allow for mutation of
|
||||
|
Loading…
Reference in New Issue
Block a user