rust/comprehensive-rust
1
0
Fork 0
mirror of https://github.com/google/comprehensive-rust.git synced 2025-04-24 16:42:36 +02:00
Code Issues Releases Activity

Move mpsc::Sender to the list of Send + Sync types (#1930)

Browse Source 
As of 1.72.0, `mpsc::Sender` [is
`Sync`](https://doc.rust-lang.org/std/sync/mpsc/struct.Sender.html#impl-Sync-for-Sender%3CT%3E).
This commit is contained in:
rbehjati 2024-03-22 14:27:11 +00:00 committed by GitHub
parent 4726252989
commit 6b3eb83bff
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/concurrency/send-sync/examples.md
View File

@ -9,6 +9,7 @@ Most types you come across are `Send + Sync`:
- `String`, `Option<T>`, `Vec<T>`, `Box<T>`, ...
- `Arc<T>`: Explicitly thread-safe via atomic reference count.
- `Mutex<T>`: Explicitly thread-safe via internal locking.
- `mpsc::Sender<T>`: As of 1.72.0.
- `AtomicBool`, `AtomicU8`, ...: Uses special atomic instructions.
The generic types are typically `Send + Sync` when the type parameters are
@ -19,7 +20,6 @@ The generic types are typically `Send + Sync` when the type parameters are
These types can be moved to other threads, but they're not thread-safe.
Typically because of interior mutability:
- `mpsc::Sender<T>`
- `mpsc::Receiver<T>`
- `Cell<T>`
- `RefCell<T>`