bounded and unbounded functions don't need to exist. There could be a single `fn new(bound: Option<usize>)`. Easier to find where to start.
-
-
-
True, although I still prefer `channel::unbounded()` because it's clearer than `channel::new(None)`
- 3 more replies
New conversation -
-
-
oh wow this is like .... everything i've wanted for mpsc thanks so much for working on this!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
apologies for rx/tx, even though it was an improvement over the previous name covention (not that I can remember what they used to be, just that they were ambiguous) :P
-
The old names were port/chan.
- 3 more replies
New conversation -
-
-
Impressive work! I am all in with the complete revamp and implementation you propose!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Good writeup! I would still love a fast spsc channel/queue in the standard library as well
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Given that Future is coming to the stdlib, maybe there is a variation on this proposal that would bring async channels instead/as-well? I don't know about the impl, but `futures::sync::mpsc` has been useful in our async code.
-
i should note that futures::sync::mpsc has a number of known issues/foot-guns (mostly around cloning and backpressure). we're in the process of moving most of our usage over to https://docs.rs/tokio-sync/0.1.3/tokio_sync/ …
End of conversation
New conversation -
-
-
If we're going to have new channels module, then it should be async aware too, there is no need to cope-paste crossbeam just for regular channels as with async/await it is going to be also important to have channels that work with std tasks well
-
From my understanding async/await channels would require different underlying mechanisms, and the design space for those hasn't been fully explored yet. It probably needs a few years in user space before they can be stabilized.
End of conversation
New conversation -
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.