I think I finally understand all moving parts of async-std's channels. But is that enough to hack on it? 
-
Show this thread
-
Replying to @yoshuawuyts
With std channels, async-channels, crossbeam, tokio channels and flume I would really appreciate one of your excellent comparison blog posts.
1 reply 0 retweets 0 likes -
Replying to @hoodie_de
https://blog.yoshuawuyts.com/streams-concurrency/ … goes into much detail on various stream models. Crossbeam supports both bounded / unbounded channels. Async-std only bounded. Async-std's channels are very flexible because MPMC. Only missing functionality is a "broadcast" method to send to all receivers
1 reply 0 retweets 2 likes
I don't know anything about Flume so can't comment. Once "broadcast" lands for async-std channels it'll basically be able to cover any topology (1:1, 1:m, m:1, m:n). With the caveat that it's bounded, which should be the right fit for the vast majority of workloads.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.