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
In 0.46.0 onwards, the read traits were removed from Reader and pushed into methods like into_futures_async_read and read. However, support for the Tokio I/O traits was lost in the process.
Is there any interest in supporting these with feature gating? For now I've been using async-compat to work around this.
The text was updated successfully, but these errors were encountered:
There is a plan to implement into_tokio_async_read() -> TokioAsyncReader. However, I am not confident that adding a feature gate at the Reader level is a good idea.
Since there is a workaround for this, how about we leave this issue open to collect more feedback?
Hello,
In 0.46.0 onwards, the read traits were removed from
Reader
and pushed into methods likeinto_futures_async_read
andread
. However, support for the Tokio I/O traits was lost in the process.Is there any interest in supporting these with feature gating? For now I've been using async-compat to work around this.
The text was updated successfully, but these errors were encountered: