Bartosz Grabias

You know, in Poland people mostly assume that Polish translations of apps (especially the less/not commercial/popular on the homelab scene ones) are either bad or terrible. You’ve made such a...

I don't know if this is a correct issue for raising this concern, but it seems related. Currently the `read_all_registers` function is generated as just calling read on each register...

The easiest "fix" for me would be to have a way of disabling generation of that method or having the option of providing a method that is called in between...

> Unless you have a proposal to add a readiness concept to the crate, I don't think I can help much more. Actually, I've been thinking about that, as different...

What about an iterator like interface for fields of the same input/output type? ```rust fn execute(&mut self, plan: impl IntoIterator): impl Iterator {} ``` I guess for async that would...

> I see your vision. For most C HALs this would totally suffice. However in rust's embedded hal, you got things like [SpiDevice](https://docs.rs/embedded-hal/1.0.0/embedded_hal/spi/trait.SpiDevice.html) that requires all operations up front. So...

How about passing in a buffer to work with and the ability for the driver to fail at runtime due to too small buffer? For majority of users, it will...

> > That is a use case requirement, not a device requirement though. Similarly, when you're developing on a device with 4-8 kB of RAM and you just can't spare...

So, unfortunately this week has been very hectic, but I did manage to put up a little something. On high level it gives API like this: ```rust let mut device...