You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on a no_std embedded comms stack which talks to devices running C applications. The stack uses heapless::Vecs to handle the byte streams being sent and received, and I would like to use bincode to perform the conversion to / from Rust structures.
Right now, in order to do this I have to create a wrapper type around the heapless::Vec in order to implement bincode's Writer and Reader traits. It seems like this is a common enough pairing that it would make sense to have these traits implemented for heapless::Vec by default, or at least available through a feature, rather than having to re-implement for each new project working in this space.
I'm not sure whether it would make more sense for this implementation to live in the bincode crate or the heapless crate, so I've created an equivalent issue on the bincode repo. What do you think?
The text was updated successfully, but these errors were encountered:
Yeah agreed, to me it would seem like it would make more sense for the implementation to live in the serialiser's crate rather than the collection's crate. Good to know there's precedent.
I am working on a no_std embedded comms stack which talks to devices running C applications. The stack uses
heapless::Vec
s to handle the byte streams being sent and received, and I would like to usebincode
to perform the conversion to / from Rust structures.Right now, in order to do this I have to create a wrapper type around the
heapless::Vec
in order to implementbincode
'sWriter
andReader
traits. It seems like this is a common enough pairing that it would make sense to have these traits implemented forheapless::Vec
by default, or at least available through a feature, rather than having to re-implement for each new project working in this space.I'm not sure whether it would make more sense for this implementation to live in the
bincode
crate or theheapless
crate, so I've created an equivalent issue on thebincode
repo. What do you think?The text was updated successfully, but these errors were encountered: