Hanno Braun

Okay, I realize we're not really talking about the same thing. This is my fault, as my comments were misleading. And because I didn't realize that until now, I misunderstood...

I'd like to nominate #249 as a blocker for the 1.0 release.

@rust-embedded/hal Would you consider releasing 1.0-alpha.2? I'm working on a driver that I'd like to release soon, and it would be great if I had access to `PinState`.

I've recently learned something that I'd like to share, in case it isn't common knowledge yet: A `cargo update` will pick up alpha.2, if alpha.1 is specified in `Cargo.toml`. I...

Oh yeah, for a moment I completely forgot that you could do that. Seems to be a good way to work around the issue! (Although in general, the situation is...

> Yeah, plus if you use alpha versions for production code, you should be aware that things might break at any time But that issue affects not only those running...

Regarding question 3: In the other thread, I [proposed a set of traits](https://github.com/japaric/embedded-hal/pull/67#issuecomment-380410443) that allow us to catch errors at compile-time. Those won't work in practice, as it's impossible to...

Another question: 4. Should error types be implementation-defined as associated types, or should we pre-define error enums? @jonas-schievink [makes an argument](https://github.com/japaric/embedded-hal/pull/67#discussion_r196561833) that errors for `cancel` need to be well-defined. A...

I don't have a solution for the problem at hand, but I'd like to provide some context about the underlying problem. This style of representing pin types, generating one type...

Partially related discussion: #24 See also (from the linked issue): https://github.com/TheZoq2/embedded-hal-time