Impl futures::stream::Stream for Controller/Listener #71
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the example tokio usage in #45 it spawns an async task for each controller,
I thought it would be nice to be able to treat each controller as a stream and poll all controllers from a
StreamMap
, I implemented stream forListener
too, but didn't actually end up using it.This allows something to the effect of the following to work, with the
Controller
automatically removed from the stream map onEvent::Disconnect
.The main reason I added it in it's own feature is because it adds a new dependency on the
futures
crate.Given that I wasn't sure if you would not want it to be in by default.