Austin Glaser

The buffer-copy issue is one that I've run into time and again with embedded C code. It would be really cool if Rust provided a way to elegantly deal with...

Totally onboard with improved ergonomics as well.

I think a way to read the pin's state is critical -- with it, for instance, you could build a portable bit-banged I2C implementation on top of a `TriStatePin`. What...

@japaric I see what you're going for in principle here. I do think that there needs to be some discussion about reading the state of an output pin, however. Depending...

@therealprof Indeed... but some do. Maybe the right place isn't in `TriStatePin`, but there should be some way at the trait level to express that a particular pin can be...

That's a compelling idea. My first thought, though, is: "how do you read back something like a `TriState` pin?" Do you have a separate `impl TriStateReadbackPin: TriStatePin` trait? This would...

Although that's starting to look a lot like (exactly like?) an `InputPin` -- maybe it's more of an implementation level thing, which encourages (where possible) the implementation of `InputPin` for...

What I've been talking about is actually reading the *electrical state* of an output pin. For cases where that makes sense (as I've said before, one such example is a...

I'm in favor of keeping the base `Read` and `Write` traits as simple as possible -- they should have to do with transmitting and receiving bytes on the bus, and...

I've got a related PR open for `stm32f30x-hal` (https://github.com/japaric/stm32f30x-hal/pull/14), which has been hanging fire since I've had no free time to test it on hardware. It implements method 2. With...