Release on crates.io about embedded-hal HOT 2 CLOSED

What's currently blocking the release of this crate on crates.io?

We are missing digital I/O traits (I smuggled in an OutputPin trait while no one was looking, though) and those are like the most common kind of I/O.

I'd like to see a resolution to RFC #18 so we can define the module hierarchy in this crate. (Or perhaps the blocking / higher level traits should be in a different crate, IDK)

We need to figure out some way to indicate the stability of the traits (IDK if #[unstable] is now available for user libraries) so we can distinguish between "this is our first stab at an abstraction for this peripheral, anything goes" and "we are 50%+ sure this abstraction won't suffer a breaking change the next week". We could use a non-default "unstable" Cargo feature; put all the unstable API behind that feature and reserve the right to break that unstable API in patch releases.

from embedded-hal.

Thanks for the info!

We need to figure out some way to indicate the stability of the traits (IDK if #[unstable] is now available for user libraries)

It doesn't seem to be. There's an open issue.

We could use a non-default "unstable" Cargo feature; put all the unstable API behind that feature and reserve the right to break that unstable API in patch releases.

I think that sounds like a workable solution.

from embedded-hal.