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'm wrapping Receiver::recv and Sender::send in structs. Because they're async fn instead of manual Future impls they require boxing when stored. It'd be nice if we could expose two new types:
RecvFuture
SendFuture
These would not require boxing, which means they can be inlined in implementations and would increase overall perf when wrapping async-channel. Given the simplicity of send and recv I suspect the implementation to be rather straight forward.
Thanks!
The text was updated successfully, but these errors were encountered:
I'm wrapping
Receiver::recv
andSender::send
in structs. Because they'reasync fn
instead of manual Future impls they require boxing when stored. It'd be nice if we could expose two new types:RecvFuture
SendFuture
These would not require boxing, which means they can be inlined in implementations and would increase overall perf when wrapping
async-channel
. Given the simplicity ofsend
andrecv
I suspect the implementation to be rather straight forward.Thanks!
The text was updated successfully, but these errors were encountered: