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

optionalise worker pool output #50

Closed
plastikfan opened this issue Aug 28, 2023 · 0 comments · Fixed by #51
Closed

optionalise worker pool output #50

plastikfan opened this issue Aug 28, 2023 · 0 comments · Fixed by #51
Assignees
@plastikfan
Labels
feature New feature or request

Comments

@plastikfan
Copy link
Contributor

plastikfan commented Aug 28, 2023 •
edited
Loading

Sometimes, a client is not interested in the output results of the worker pool, so forcing them to use a consumer for info they're not interested in is a bit cumbersome. The client should be able to switch off consumption requirement, so that the workers do not send anything to the output channel.

This optionality will be controlled by the value of the output channel provided. If the channel is nil, then no outputs will be generated.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@plastikfan plastikfan

Labels
feature New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(async): optionalise worker pool output (#50) snivilised/lorax
1 participant
@plastikfan