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
Right now, all the functions support Read and Write traits. When using async Rust, it would probably be better to support AsyncRead and AsyncWrite. I wonder if that's something you'll be willing to accept.
We can obviously feature flag this, and make it experimental at first. But I wanted to know what you think.
Acceptance Criteria
Supporting AsyncRead implementations in ciborium
Supporting AsyncRead in ciborium-ll, or even Stream?
Suggestions for a technical implementation
Having a future feature flag to not add burden of current apps that don't need async support.
The text was updated successfully, but these errors were encountered:
Serde doesn't have a mechanism for restarting once an error has happened, so supporting async traits for the serde portion of the library doesn't make sense. For the low level library, I think it would be sufficient for it to work on &[u8], since the library doesn't block in any other way.
Is there an existing issue for this?
Description
Right now, all the functions support
Read
andWrite
traits. When using async Rust, it would probably be better to supportAsyncRead
andAsyncWrite
. I wonder if that's something you'll be willing to accept.We can obviously feature flag this, and make it experimental at first. But I wanted to know what you think.
Acceptance Criteria
AsyncRead
implementations in ciboriumAsyncRead
in ciborium-ll, or evenStream
?Suggestions for a technical implementation
Having a
future
feature flag to not add burden of current apps that don't need async support.The text was updated successfully, but these errors were encountered: