embassy - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Rename examples/nrf to examples/nrf52840	Dominik Boehi	2023-01-09	1	-43/+0
\|
*	sync: flatten module structure.	Dario Nieuwenhuis	2022-08-22	1	-1/+1
\|
*	split `embassy-util` into `embassy-futures`, `embassy-sync`.	Dario Nieuwenhuis	2022-08-22	1	-2/+2
\|
*	Split embassy-time from embassy-executor.	Dario Nieuwenhuis	2022-08-18	1	-2/+2
\|
*	Remove HAL initialization from #[embassy::main] macro.	Dario Nieuwenhuis	2022-08-17	1	-2/+2
\|
*	Split embassy crate into embassy-executor, embassy-util.	Dario Nieuwenhuis	2022-07-29	1	-6/+6
\|
*	Run rustfmt.	Dario Nieuwenhuis	2022-06-12	1	-3/+1
\|
*	Rename channel to mpmc	huntc	2022-06-12	1	-1/+1
\| \| \| \|	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.
*	Simpler Channel.	Dario Nieuwenhuis	2022-04-06	1	-0/+45
	- Allow initializing in a static, without Forever. - Remove ability to close, since in embedded enviromnents channels usually live forever and don't get closed. - Remove MPSC restriction, it's MPMC now. Rename "mpsc" to "channel". - `Sender` and `Receiver` are still available if you want to enforce a piece of code only has send/receive access, but are optional: you can send/receive directly into the Channel if you want.