Trouble embedding a BoxFuture in an OwningHandle

I'm trying to use an OwningHandle (from the owning_ref crate) to combine the ownership of a byte array with the ownership of a future that uses that byte array. This is a toy example, the real use case is in a larger program that re-uses aligned I/O buffers when doing async disk reads and writes into those buffers. The goal is to get the buffer and the future together into an object that I can put into vectors to track operations in flight and implement futures::Stream classes that consume them and yield the results.

The code below doesn't compile, with the error:

error[E0599]: no method named `as_mut` found for reference `&OwningHandle<Vec<u8>, Pin<Box<dyn futures::Future<Output = Result<usize, std::io::Error>> + std::marker::Send>>>` in the current scope
  --> src/
28 |         let inner_fut = future_handle.as_mut();
   |                                       ^^^^^^ method not found in `&OwningHandle<Vec<u8>, Pin<Box<dyn futures::Future<Output = Result<usize, std::io::Error>> + std::marker::Send>>>`

error: aborting due to previous error; 6 warnings emitted

It seems like I should be able to deref into the OwningHandle to get a BoxFuture, and then call .as_mut() on the BoxFuture to get a Pin<&mut dyn Future> that I can poll on. I've tried a few different permutations on dereferencing the OwningHandle explicitly with .deref(), but haven't stumbled upon something that works.

Any help much appreciated! This is my first time trying to use OwningHandle and futures together this way, and it's stretching the limits of how much I understand the types in play here.

extern crate owning_ref;

use std::ops::Deref;
use std::pin::Pin;
use std::task::{Context, Poll};

use futures::future::BoxFuture;
use owning_ref::OwningHandle;

// An OwningHandle for bundling a Future together with the Vec that it's
// using as an I/O buffer.
type FutureHandle<'a> = OwningHandle<Vec<u8>, BoxFuture<'a, std::io::Result<usize>>>;

/// A demonstration Stream type that yields the result from a FutureHandle
struct MyStream<'a> {
    future_handle: Option<FutureHandle<'a>>,

impl<'a> futures::Stream for MyStream<'a> {
    type Item = std::io::Result<usize>;

    fn poll_next(mut self: Pin<&mut Self>, cx: &mut Context<'_>) -> Poll<Option<Self::Item>> {
        let future_handle = match self.future_handle.as_ref() {
            None => return Poll::Ready(None),
            Some(fh) => fh,

        let inner_fut = future_handle.deref_mut();
        match inner_fut.poll() {
            Poll::Pending => Poll::Pending,
            Poll::Ready(i) => {
                self.future_handle = None;

// A placeholder for an I/O operation: IRL this would be something like a socket read
async fn operate(buffer: &[u8]) -> std::io::Result<usize> {
    let i = buffer[0];

fn main() {
    let buffer: Vec<u8> = Vec::from([0xff; 16]);

    let handle: FutureHandle<'_> =
        OwningHandle::new_with_fn(buffer, |buffer| -> BoxFuture<'_, std::io::Result<usize>> {
            unsafe {
                let slice = &buffer.as_ref().unwrap()[0..16];

    let stream = MyStream {
        future_handle: Some(handle),


There a couple of problems with your approach:

  • future_handle is a shared reference, you need an exclusive one to call deref_mut. To do this you have to change that as_ref into an as_mut
  • OwningHandle implements DerefMut only if its second generic parameter implements DerefMut, however you second generic parameter is a Pin, and it doesn't implement DerefMut unless the target of its inner type implements Unpin, which is not the case here.

If retrieving the buffer is not a concern (doesn't look like it is since it is dropped when set self.future_handle = None) then you should be able to get away with just moving buffer into an async move { ... } block (playground).
If however you want to retrieve it after the future has yielded Poll::Ready then I would use the ouroboros crate instead of owning_ref (playground).


Thank you, this is a very helpful response.

The approach of moving buffers into an async move works, but as you say, makes it harder to reclaim the buffer reliably. I hadn't heard of ouroboros before, so I'll take a look at that.