Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/katyo/extern_executor
Rust async executor which delegates execution to external event loop
https://github.com/katyo/extern_executor
Last synced: 2 months ago
JSON representation
Rust async executor which delegates execution to external event loop
- Host: GitHub
- URL: https://github.com/katyo/extern_executor
- Owner: katyo
- Created: 2020-04-17T12:25:02.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2023-06-17T10:40:13.000Z (over 1 year ago)
- Last Synced: 2024-09-16T17:53:54.220Z (4 months ago)
- Language: Rust
- Size: 82 KB
- Stars: 5
- Watchers: 2
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# External executor for async Rust
[](https://opensource.org/licenses/MIT)
[](https://crates.io/crates/extern_executor)
[](https://docs.rs/extern_executor)
[](https://travis-ci.com/katyo/extern_executor)
This project aims to provide simple executor which helps to delegate running asynchronous Rust code to external event loops.
As example, it may be useful in case when you develop dynamic linked libraries which have async code in Rust and want to run it in different execution environments.
## Usage
On a Rust side you should add `extern_executor` as dependency to your `cdylib` crate and use `spawn()` function to run futures, like so:
```rust
use extern_executor::spawn;
spawn(async {
// your awaits
});
```
On a C side you should implement executor's driver using your preferred event loop API.
For example, when [libuv](https://github.com/libuv/libuv) is used it may looks like so:
```c
#include
#include
static void task_wake(RustAsyncExecutorExternTask data) {
uv_async_t* handle = data;
// wakeup uv's async task
uv_async_send(handle);
}
static void task_poll(uv_async_t* handle) {
// poll internal task until task complete
if (!rust_async_executor_poll(handle->data)) {
// drop internal task when task complete
rust_async_executor_drop(handle->data);
// drop uv's async task handle
uv_close((uv_handle_t*)handle, NULL);
}
}
static RustAsyncExecutorExternTask
task_new(RustAsyncExecutorUserData data) {
uv_loop_t* loop = data;
// crate and initialize uv's async task handle
uv_async_t* handle = malloc(sizeof(uv_async_t));
uv_async_init(loop, handle, task_poll);
return handle;
}
static void task_run(RustAsyncExecutorExternTask task,
RustAsyncExecutorInternTask data) {
uv_async_t* handle = task;
// store internal task handle to be able to poll it later
handle->data = data;
uv_async_send(handle); // do initial polling (important)
}
void uv_rust_async_executor_init(uv_loop_t *loop) {
// send out executor API to Rust side
rust_async_executor_init(task_new, task_run, task_wake, loop);
}
```
Now you can run your async code in __libuv__'s event loop like so:
```c
int main(void) {
uv_loop_t loop;
uv_loop_init(&loop);
uv_rust_async_executor_init(&loop);
my_async_function(my_async_callback);
uv_run(&loop, UV_RUN_DEFAULT);
uv_loop_close(&loop);
return 0;
}
```
The C header _rust_async_executor.h_ generated using [cbindgen](https://github.com/eqrion/cbindgen/).
There are two options how you can get it:
* Copy from _include_ directory in this repo
* Generate by youself by using _cbindgen_ feature
In second case generated header will be available at `target/$PROFILE/include` directory.
## Built-in event-loop drivers
To simplify setup for some widely used event loops the built-in drivers was introduced.
To use driver you should enable corresponding feature. Currently supported next drivers:
- __uv__ built-in _libuv_ event loop integration (see [example_uv](http://github.com/katyo/extern_executor/tree/master/example_uv))
- __dart__ built-in _dart-lang_ event loop integration (see [example_dart](http://github.com/katyo/extern_executor/tree/master/example_uv))
## Linking issues
Rust currently have an issues related to re-exporting of symbols from crate's dependencies (#[2771](https://github.com/rust-lang/rfcs/issues/2771)).
As temporary solution you can setup build profile like so:
```toml
[profile.release]
lto = true
incremental = false
```
## Tokio compatibility
This executor incompatible with [tokio](https://github.com/tokio-rs/tokio)'s futures because _tokio_ still has non-trivial executor which mixed with reactor.