Open elast0ny opened 10 months ago
We'll have at least one more breaking change when Error becomes a subtrait of core::Error. I'm also not sure WriteReady are ready (ha!) for prime time.
Maintainers, we use this issue as a tracking issue to list what has to be done before -io 1.0?
Hello, I'm working on a project that is considering using
embedded-io
's traits forno_std
environments and had some concerns about the stability of the API.For example, the popular
postcard
serde format supportsembedded-io
traits but only from version0.4.0
. This means that I either have to commit to an old version to usepostcard
or make a fork ofpostcard
(and upstream fixes ideally). I assume this is a decision that anyone in theno_std
ecosystem has to make if they want to be generic overRead/Write
.Is there any chance that
embedded-io
could take a stance on backwards compatibility of itsRead/Write
traits (as a statement in aREADME
perhaps) and make a release of major version1
?I understand that the crate may not be in such a state to be stable "forever" but if so, it would provide much more confidence in committing to using it.