-
xtra is by design small and thus, I think a big contestor for people making a decision on what to use might be tokio's or futures' mpsc channels, spawned as a task with an endless loop.
It would be…
-
Actors initially were taking an excessive amount of memory for each instance. This is a tracking issue to reduce memory and increase processing time latencies in the actor framework.
Some ideas
…
-
Currently, the `SendRef` and `RecvRef` types returned by `thingbuf::mpsc`'s senders and receivers contain a borrowed reference to the channel's queue. This means that a `Ref` from a channel cannot liv…
hawkw updated
2 years ago
-
@trustin has done some interesting work in netty/netty#2529 (although we’ll want to keep the Unsafe bits).
rkuhn updated
8 years ago
-
# Simple channels example in rust using tokio::sync::mpsc.
[https://www.vivek.ink/posts/simple-channels-mpsc/](https://www.vivek.ink/posts/simple-channels-mpsc/)
-
Queue semantics don't offer object reuse. Having to allocate new object instance for every offer() call effectively halves queue throughput.
It would be useful to have disruptor-like pattern around a…
-
cf. https://github.com/crossbeam-rs/crossbeam/pull/189
-
```rust
use std::{mem::forget, sync::mpsc};
use generator::Gn;
fn main() {
let mut s = "Happy".to_owned();
let (tx1, rx1) = mpsc::sync_channel(1);
let (tx2, rx2) = mpsc::sync_cha…
-
We're exploring options in the logging space. I was curious how amenable you folks would be to using std::sync::mpsc::sync_channel in favor of crossbeam?
-
### What it does
A lint which checks for blocking functions inside an async block.
One I know of (and the cause of a bug I ran into today) is `std::thread::sleep`, but there are others. (file operat…