Thomas Eizinger
Thomas Eizinger
> > I opened an issue with `either` to see if we can get `AsyncRead` + `AsyncWrite` traits. Then we could drop the `EitherOutput` type: [bluss/either#79](https://github.com/bluss/either/issues/79) > > Update: As...
> The bottom line is that I think we should convince `either` that they should provide a `Future` etc implementation that doesn't try to be clever but simply sets all...
`EitherFuture` is here to stay for a while so I am considering this to be completed because everything that is actionable has been done.
Considering this as resolved.
I guess we can close this as stale.
Let me know if you still want to contribute some new examples.
Closing this as we will likely ship this in a different PR, thanks kicking it off @MarcoPolo ! See https://github.com/libp2p/rust-libp2p/pull/3651 and related PRs for further progress!
Tagging this as important because it performs IO on the main task that all `NetworkBehaviour`s run on.
Let me know if still an issue.