ryan

> How does a trait like this look? ```rust pub trait ConfigureBaud { type BaudRate; type Error; fn set_baud_rate(&mut self, baud_rate: BaudRate) -> Result; } ``` seems broadly good to...

v1/v2 traits have been removed in `v1.0.0` (#177) which I believe resolves this issue

i have mixed feelings about async being separate in the long term, but imo it very much depends whether we can find an approach (as is the case for one...

Thanks for the reminder, shipped in #255

howdy, thanks for the issue! the main goal with `e-h` is to abstract what is required for [drivers](https://docs.rs/embedded-hal/latest/embedded_hal/#design-goals) rather than how to interact with a given platform, because that differs...

hey thanks for the issue / PR! I haven't used PWM capture in some time, @rust-embedded/hal team any thoughts about this?

requiring `From` would be a neat solve, though, there are some [drawbacks](https://github.com/fluentech/embedded-time#duration) to `core::time::Duration` for embedded use. we could perhaps look to using `embedded_time::Duration` for this bound?

hmm, interesting. afaik most processors have some bitband registers that should make that _more_ efficient than otherwise, but it's still not _always_ going to be efficient. what about a single...

hi, sounds like an interesting project! > Is there a plan to add a I2S interface in the embedded-hal project yet? As far as I know there is not yet....

uhoh, that shouldn't happen. the related line is [here](https://github.com/rust-embedded/embedded-hal/blob/384b4934a88a7939604ca7cf4048c49a4cd07c16/src/digital/v2_compat.rs#L75). we provide a polyfill from v1 to v2 types for forward compatibility (though this is all going away, and changing, in...