mirror of
https://github.com/rust-lang/rust-clippy
synced 2024-11-24 05:33:27 +00:00
Documentation edits for arc_with_non_send_sync
Arc's documentation uses the term "thread", aligning to that terminology. Fix typo in "Rc".
This commit is contained in:
parent
3b8323d790
commit
c2d071c11c
1 changed files with 2 additions and 2 deletions
|
@ -14,8 +14,8 @@ declare_clippy_lint! {
|
||||||
/// This lint warns when you use `Arc` with a type that does not implement `Send` or `Sync`.
|
/// This lint warns when you use `Arc` with a type that does not implement `Send` or `Sync`.
|
||||||
///
|
///
|
||||||
/// ### Why is this bad?
|
/// ### Why is this bad?
|
||||||
/// `Arc<T>` is an Atomic `RC<T>` and guarantees that updates to the reference counter are
|
/// `Arc<T>` is an Atomic `Rc<T>` and guarantees that updates to the reference counter are
|
||||||
/// Atomic. This is useful in multiprocessing scenarios. To send an `Arc<T>` across processes
|
/// Atomic. This is useful in multithreading scenarios. To send an `Arc<T>` across threads
|
||||||
/// and make use of the atomic ref counter, `T` must be [both `Send` and `Sync`](https://doc.rust-lang.org/std/sync/struct.Arc.html#impl-Send-for-Arc%3CT%3E),
|
/// and make use of the atomic ref counter, `T` must be [both `Send` and `Sync`](https://doc.rust-lang.org/std/sync/struct.Arc.html#impl-Send-for-Arc%3CT%3E),
|
||||||
/// either `T` should be made `Send + Sync` or an `Rc` should be used instead of an `Arc`
|
/// either `T` should be made `Send + Sync` or an `Rc` should be used instead of an `Arc`
|
||||||
///
|
///
|
||||||
|
|
Loading…
Reference in a new issue