Skip to content

Clarify the Behavior of FuturesUnordered on Error #642

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.

Sign up for GitHub

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

Jump to bottom
Closed
cramertj opened this issue Nov 14, 2017 · 1 comment
Closed

Clarify the Behavior of FuturesUnordered on Error #642

cramertj opened this issue Nov 14, 2017 · 1 comment

Comments

@cramertj
Copy link
Member

When polling a list of futures in FuturesUnordered, it is often nice to be able to receive and log errors that arise from some of the child futures without ceasing to poll the whole structure. This works currently, however this behavior is unusual in for a Stream and is undocumented.

Is this behavior that FuturesUnordered intends to support? If so, I'll open a PR documenting this functionality.
@cramertj
Copy link
Member Author

I suppose this probably falls out of not having #206, so closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cramertj