From 99d19c7dcf077cdd06113bf013d6a458289b1ecb Mon Sep 17 00:00:00 2001 From: huntc Date: Sun, 12 Jun 2022 15:16:56 +1000 Subject: 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. --- examples/stm32f3/src/bin/button_events.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'examples/stm32f3/src/bin') 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; -- cgit v1.2.3