manual-executor 0.1.0

Async executor with manual waking
Documentation
  • Coverage
  • 0%
    0 out of 3 items documented0 out of 0 items with examples
  • Size
  • Source code size: 553.19 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 602.23 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Links
  • elmerbulthuis/manual-executor
    1 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • elmerbulthuis

Manual Executor

Manual Executor

This is a manual executor for driving futures to readiness. You need to manually wake the futures! But of course what else dit you expect from an executor that is called manual-executor. Because of the manual nature the use cases of this executor are limited.

It was built to be used via ffi (also wasm). Imagine a library that wants to do a http-request. It has no way of doing it except via the host. So the host exposes a fetch function that does the http-request. This is all done asynchronously. How does the library know when the fetch function is done? That problem is solved with the manual-executor. The host simply calls the wake (or wake_all if you are a bit sloppy) function with the appropriate key.

coverage

Install grcov, llvm-tools.

Like this (on arch)

pacman -S grcov
rustup component add llvm-tools

You might want to manually clean up the target directory from time to time to keep grcov form not erroring...