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.

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

Create varargs versions of all fan-in/out fluent combinators in FlowOps #19045

Closed
4 tasks done
viktorklang opened this issue Nov 30, 2015 · 6 comments
Closed
4 tasks done
Labels
1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted help wanted Issues that the core team will likely not have time to work on t:stream
Milestone

Comments

@viktorklang
Copy link
Member

viktorklang commented Nov 30, 2015

  • mergeAll
  • concatAll
  • interleaveAll
  • alsoToAll
@viktorklang viktorklang added the 0 - new Ticket is unclear on it's purpose or if it is valid or not label Nov 30, 2015
@viktorklang viktorklang changed the title Create varargs versions of all fan-in fluent combinators in FlowOps Create varargs versions of all fan-in/out fluent combinators in FlowOps Nov 30, 2015
@patriknw
Copy link
Member

patriknw commented Jun 6, 2016

@drewhk is this still relevant?

@drewhk
Copy link
Member

drewhk commented Jun 7, 2016

Likely yes.

@patriknw patriknw added 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted help wanted Issues that the core team will likely not have time to work on and removed 0 - new Ticket is unclear on it's purpose or if it is valid or not labels Jul 7, 2016
@He-Pin
Copy link
Member

He-Pin commented Mar 30, 2022

@patriknw Is this issue still valid?

@patriknw
Copy link
Member

yes, the alternative with GraphDSL is not easy to use

@He-Pin
Copy link
Member

He-Pin commented Mar 30, 2022

Thanks for confirm。

@patriknw
Copy link
Member

patriknw commented Sep 1, 2022

Great work @He-Pin

@patriknw patriknw closed this as completed Sep 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted help wanted Issues that the core team will likely not have time to work on t:stream
Projects
None yet
Development

No branches or pull requests

4 participants