example of using a channel for communication#16
Open
egonelbre wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR demonstrates how channels (Go-s built-in concurrent queues) work.
Note, I'm aware you may not want to switch yet, so it's more of an educational PR, I guess.
In principle there are few things to know:
There are few other things that channels allow, for example receiving/sending from multiple queues at the same time.
As an example if we have two input ports and one output port we could implement a
less thancomponent that keeps sending the result of that comparison to output anytime one of the input values changes:Note, the code above currently does not handle closing of the incoming/outgoing connections.