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

Allow explicit close of output channels #7

Open
mariomac opened this issue Jan 17, 2023 · 0 comments
Open

Allow explicit close of output channels #7

mariomac opened this issue Jan 17, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@mariomac
Copy link
Owner

There is a maximum in golang that says:

Senders close; receivers check for close

However, output channels in pipeline stages are automatically closed. That causes that some asynchronous operations require to implement extra synchronization mechanisms to double check that the output channel is not close.

While we can keep automatic close of channels by default, we can provide an extra graph/node builder argument to allow explicit closing of output channels.

@mariomac mariomac added the enhancement New feature or request label Jan 17, 2023
@mariomac mariomac changed the title Force explicit close of output channels Allow explicit close of output channels Jan 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant