desync

desync copied to clipboard

More unsoundness in `future_sync` and `future_desync`

6

From PR #7: > Actually, there's more soundness bugs with the signatures of the future_[de]sync() methods. To illustrate: > > ```Rust > use desync::Desync; > use futures::executor; > > fn...

Logicalshift

Getting Rid of 'static

1

Hi, Right now the signature for the future is ```rust pub fn future(&self, job: TFn) -> impl Future+Send where TFn: 'static+Send+for BoxFuture impl 'a + Future+Send where TFn: 'a+Send+FnOnce(&'a mut...

anlumo

Pipe sometimes skips sent item

2

Hi, I had a code like this: ``` let (mut sender, stream) = mpsc::channel(1000); tokio::task::spawn(async move { while { let item = ... sender.send(item).await.unwrap(); } }); let stream2 = pipe(Arc::new(Desync::new(0)),...

mpskowron

Getting Rid of Send Requirement

1

Hello, Correct me if I'm wrong, but it looks to me like the only reason why the type stored in the Desync has to be `Send` is that it's passed...

anlumo

Hi, The following code causes panic, saying `thread 'desync jobs thread' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime'` ```rs...

overflowz