-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
i2c: enforce all traits have the same Error type. #336
Conversation
r? @therealprof (rust-highfive has picked a reviewer for you, use r? to override) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thanks!
dd68891
to
bd6a047
Compare
bd6a047
to
8bad7f5
Compare
8bad7f5
to
7e59a5e
Compare
Friendly ping @eldruin @therealprof @ryankurte are there any pending concerns on this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, too.
bors r+
339: I2c unify r=eldruin a=Dirbaio Depends on #336 Equivalent of #323 but for I2c. I think for i2c unifying everything in a single trait makes the most sense. The i2c bus is specified to be bidirectional, I believe no hardware out there can "only write" or "only read" (and writing requires *reading* ACK bits anyway!). Co-authored-by: Dario Nieuwenhuis <dirbaio@dirbaio.net>
Equivalent of #331 for i2c.