diff options
| author | huntc <huntchr@gmail.com> | 2022-06-12 15:16:56 +1000 |
|---|---|---|
| committer | huntc <huntchr@gmail.com> | 2022-06-12 15:16:56 +1000 |
| commit | 99d19c7dcf077cdd06113bf013d6a458289b1ecb (patch) | |
| tree | 21344af53a0823f4949b25dbd2d9011ffe316f8a /examples/stm32f3/src/bin | |
| parent | db344c2bda55bd0352a43720788185cc4d3a420e (diff) | |
| download | embassy-99d19c7dcf077cdd06113bf013d6a458289b1ecb.zip | |
Rename channel to mpmc
I've renamed the channel module for the MPMC as mpmc. There was a previous debate about this, but I feel that the strategy here avoids importing `channel::channel`. The change leaves `signal::Signal`, but I think that's ok. It is all a bit subjective of course. The bottom line for me is that I really like the term mpmc - it means something to me and aligns with broader naming e.g. in Tokio.
Diffstat (limited to 'examples/stm32f3/src/bin')
| -rw-r--r-- | examples/stm32f3/src/bin/button_events.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/examples/stm32f3/src/bin/button_events.rs b/examples/stm32f3/src/bin/button_events.rs index 06e8eec1..59370179 100644 --- a/examples/stm32f3/src/bin/button_events.rs +++ b/examples/stm32f3/src/bin/button_events.rs @@ -12,7 +12,7 @@ use defmt::*; use embassy::blocking_mutex::raw::ThreadModeRawMutex; -use embassy::channel::channel::Channel; +use embassy::channel::mpmc::Channel; use embassy::executor::Spawner; use embassy::time::{with_timeout, Duration, Timer}; use embassy_stm32::exti::ExtiInput; |