Skip to content
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

Stream::filter_map should use IntoFuture on its closure #338

Closed
alexcrichton opened this issue Jan 10, 2017 · 3 comments
Closed

Stream::filter_map should use IntoFuture on its closure #338

alexcrichton opened this issue Jan 10, 2017 · 3 comments
Labels
C-feature-request

Comments

@alexcrichton
Copy link
Member

Tagging for an 0.2 release to ensure we don't forget it. We're doing this everywhere else with Stream, so may as well be consistent.
@alexcrichton alexcrichton added this to the 0.2 release milestone Jan 10, 2017
@alkis
Copy link

alkis commented Dec 22, 2017

Can we get a filter_map2 as a stop gap until 0.2 lands?

@alexcrichton
Copy link
Member Author

For now I'd recommend vendoring a local extension trait/combinator, but if there's enough desire we could consider a new method!

@cramertj cramertj mentioned this issue Feb 5, 2018
Merged
@alexcrichton
Copy link
Member Author

This landed in #726 for 0.2, 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
C-feature-request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alexcrichton @alkis