-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tokio support #5
Comments
That's currently provided through What would be the difference with implementing |
I might be missing something, but last time I looked at how As a slightly related side note, when I discussed my code on the tokio gitter, I was told the In that sense, having a |
That's a good point, I'd be fine with a feature-gated |
Hello
As mentioned in #4, I just created a „competing“ crate, whithout the intention to compete with anyone. I have a minimal implementation for async with tokio, which I wanted to extend in the future. It works by turning the interface object into an async object (which no longer supports all the fancy things like getting the name) that implements
Sink
andStream
.So, I was thinking, instead of trying to compete, would it make sense if I ported that async wrapper to this crate?
The text was updated successfully, but these errors were encountered: