Diego Barrios Romero

Thanks for noticing. I have a WIP driver for the [LSM303AGR](https://github.com/eldruin/lsm303agr-rs) so you can at least play around with that. It is actually the same accelerometer as the micro:bit board...

@waalge Sure thing. We would be glad about PRs doing that.

The one hosted at https://rust-embedded.github.io/discovery should be rebuilt shortly after each PR merge. The one hosted at https://docs.rust-embedded.org/discovery is a bit outdated because our CI for it [is currently broken](https://github.com/rust-embedded/docs/issues/29)....

Changes are still possible here. The reason I chose separate buffers for left and right instead of `[(W,W)]` is because they are much easier to deal with than an array...

We have a publication issue in our CI: ``` Traceback (most recent call last): File "./ghp-import/ghp_import.py", line 10, in from dateutil import tz ImportError: No module named dateutil ``` See...

While not the primary goal of this crate, in my opinion it is also useful if `embedded-hal` provides unified interfaces across the ecosystem for very common peripherals, where it makes...

LGTM! @thenewwazoo could you rebase this to master?

I think this question is too broad or I do not understand it. There is an implementation of `embedded-hal` for Arduino microcontrollers and boards in [`avr-hal`](https://github.com/Rahix/avr-hal).

Now that we have a clear structure for the execution models (`blocking`/`nb`), in principle I would be open to add a nightly-only `futures` module behind a `futures` (or similar) feature....

Is the proposed architecture change actually a blocker to publishing the already tagged version 4.0.0 on PyPI? Internally we are moving ahead with using the 4.0.0 version as tagged here...