pub struct AsyncTransporter { stream: Arc<dyn AsyncRW + Send + Sync>, } Suppose that a library expects AsyncTransporter to be Send + Sync, and that dyn AsyncRW is a struct that holds a channel tuple: pub struct SmolSocket { channel: (Sender<Arc<Packet>>, Receiver<Arc<Packet>>), } How can …

Rust's `Sender/Receiver` is forced to be `Sync + Send`

mbrubeck June 17, 2021, 3:16am 2

crossbeam-channel is a high-quality alternative to std::sync::mpsc, with Sender and Receiver types that are Send + Sync.

1 Like

Topic		Replies	Views
Why Arc'ed and RwLock'ed type isn't Send and Sync? help	4	1605	January 31, 2023
Why this struct is not Sync + Send? help	8	1428	March 6, 2023
Why Arc<Mutex<SomeType>> still implies SomeType must be Sync + Send? help	4	744	February 10, 2021
Why we implement Send trait for Mutex? help	12	2470	June 4, 2020
Arc and the Send bound	10	3610	January 12, 2023