Dario Nieuwenhuis

Done in #961

Errors just set the flags and reception continues: > An ERROR event will not stop reception. If the error was a parity error, the received byte will still be transferred...

Since it's a bit old, I am not planning to work on it myself, but will review and merge PRs adding support. I suppose the main annoyance will be lack...

One disadvantage of only using InterruptExecutor is you're no longer running anything in thread mode, so ThreadModeMutex becomes useless. `embassy-net` has an internal ThreadModeMutex, but removing it is probably a...

@osobiehl WFE/SEV work like this: - `sev` sets an "event" flag register - `wfe` waits until the "event" flag is set, clears it, and returns. And, more importantly: if the...

Probably not gonna happen anytime soon.

The `embedded-nal` (nb-based) traits will not be implemented. `nb` is broken by design, `async` is superior to it in every way, the Embassy project will not invest effort in `nb`....

@fralalonde try updating rustup (not rust), I think older rustups didn't take the `.toml` file.

also, would you guys consider licensing the usb host code as Apache+MIT instead? I'm interested to add in host functionality for `embassy-usb` eventually, but can't take GPL/LGPL so I'll have...

In nightly it is already possible to have async traits with `feature(generic_associated_types)`. ([example](https://github.com/akiles/nrf-softdevice/blob/52329d22febd6f19a63ab398de1dbc2a228ee3d9/async-flash/src/lib.rs#L17)). This does fully static dispatch and no heap allocations. You can even implement the traits with `async`...