tokio-async-drop 0.1.0

macro to enable async drop in a tokio multithreaded runtime
Documentation
  • Coverage
  • 0%
    0 out of 2 items documented0 out of 1 items with examples
  • Size
  • Source code size: 4.15 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 239.27 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 9s Average build duration of successful builds.
  • all releases: 9s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • nappa85/tokio-async-drop
    8 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • nappa85

tokio-async-drop

This is a quick and dirty "hack" (not really an hack, since it's the desired behaviour of used components) to allow async drop in a tokio multithreaded runtime.

The same approach could potentially be used to allow async code in many other situations, e.g. inside a once_cell::sync::Lazy static variable.

Example

struct Foo<'a> {
    inner: &'a mut u8,
}

impl<'a> Foo<'a> {
    async fn bar(&mut self) {
        tokio::time::sleep(std::time::Duration::from_secs(1)).await;
        *self.inner = 1;
    }
}

impl<'a> Drop for Foo<'a> {
    fn drop(&mut self) {
        tokio_async_drop!({
            self.bar().await;
        });
    }
}

#[tokio::main]
async fn main() {
    let mut semaphore = 0;
    let f = Foo {
        inner: &mut semaphore,
    };
    drop(f);
    assert_eq!(semaphore, 1);
}