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
Currently, async-usercalls uses an artificial MakeSendMarker trait to specify type boundaries for ByteBuffer, User<ByteBuffer>, User<[u8]> (see async-usercalls/src/utils.rs).
Instead, we could implement some of the underlying methods in those 3 types directly. This requires "upstreaming", so we'll first have to wait for async-usercalls changes to be accepted in the rust-lang repository.
The text was updated successfully, but these errors were encountered:
Currently, async-usercalls uses an artificial
MakeSendMarker
trait to specify type boundaries forByteBuffer
,User<ByteBuffer>
,User<[u8]>
(seeasync-usercalls/src/utils.rs
).Instead, we could implement some of the underlying methods in those 3 types directly. This requires "upstreaming", so we'll first have to wait for async-usercalls changes to be accepted in the rust-lang repository.
The text was updated successfully, but these errors were encountered: