Merged
Conversation
YiraSan
force-pushed
the
master
branch
3 times, most recently
from
d5dfcf4 to
4ae4054
Compare
Owner
|
Thanks! |
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
2 participants
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.
A multi-producer, multi-consumer queue for sending data between tasks, schedulers, and threads.
It supports various configurations: single-producer & multi-consumer, multi-producer & single-consumer, and single-producer & single-consumer.
Only one consumer receives each sent data, regardless of the number of consumers.
If this queue is okay I will then work on implementing a BroadcastQueue, this will pratically be the same thing, but all consumers (except the sender) will receives a copy of the sended data.