-
Notifications
You must be signed in to change notification settings - Fork 32
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
Do you have plan to implement broadcast channel? #9
Comments
Thank you! |
Broadcast channel disallows some optimizations like in-stack-transfer, which is the shining point of this extremely fast crate. If so, why not just use an existing crate async-broadcast |
I think we can do the same optimization using the signal for broadcast too. but I'm unsure to add broadcast type to Kanal. in one hand I like Kanal to be complete and featureful but in case maintaining both normal and broadcast channels together proves to be counter-productive for us. I prefer to keep Kanal away from the broadcast channels. |
Nice work!!
I think it would be nice to have a clear separation of the different kind of channels. I assume the one currently implemented is mpmc because both the sender and the receiver implements
Clone
. (Would there be a speed improvement to also implement mpsc?)I would be really interested to see an implementation for a broadcast type of channel. You send the message once, the message needs to implement
Clone
, and all the receivers receive a copy of it. Like it is done by the crate async-broadcast.The text was updated successfully, but these errors were encountered: