Merge #791
791: Channel clarification r=lulf a=diondokter This was unclear from the docs. Co-authored-by: Dion Dokter <diondokter@gmail.com>
This commit is contained in:
commit
34673f52c9
@ -3,6 +3,9 @@
|
|||||||
//! It can be used concurrently by multiple producers (senders) and multiple
|
//! It can be used concurrently by multiple producers (senders) and multiple
|
||||||
//! consumers (receivers), i.e. it is an "MPMC channel".
|
//! consumers (receivers), i.e. it is an "MPMC channel".
|
||||||
//!
|
//!
|
||||||
|
//! Receivers are competing for messages. So a message that is received by
|
||||||
|
//! one receiver is not received by any other.
|
||||||
|
//!
|
||||||
//! This queue takes a Mutex type so that various
|
//! This queue takes a Mutex type so that various
|
||||||
//! targets can be attained. For example, a ThreadModeMutex can be used
|
//! targets can be attained. For example, a ThreadModeMutex can be used
|
||||||
//! for single-core Cortex-M targets where messages are only passed
|
//! for single-core Cortex-M targets where messages are only passed
|
||||||
|
Loading…
Reference in New Issue
Block a user