Pool::run should return impl Future that is Send about bb8 HOT 5 CLOSED

Adding Send to the future returned from Pool::run would require some internal changes, and I don't really see why it's useful.

Why don't you just do something like

  let (tx, rx) = oneshot::channel();
  let f = pool.run(my_closure)
    .then(|r| tx.send(r).unwrap());
  current_thread_executor.dispatch(f);
  let f = rx.and_then(blah_blah_blah);
  do_something_requiring_send(f);

?

from bb8.

This may be possible but adds boilerplate, to the detriment of user ergonomics.

from bb8.

Sure, but there's also a cost to providing Send for those who don't need it. What are you doing that requires Send?

from bb8.

Just seeing this now (after creating #10). All futures that generate Hyper responses require Send, so the boilerplate from your comment would be needed for any code that generated Hyper responses.

from bb8.

This is partially fixed by #10, and the rest will be fixed if #8 is merged, so I'm going to close this.

from bb8.