async-executor icon indicating copy to clipboard operation
async-executor copied to clipboard

Async executor

Results 25 async-executor issues
Sort by recently updated
recently updated
newest added

`async-task` allows arbitrary metadata to be attached to tasks. It would be nice if this were available in `async-executor` as well.

enhancement
good first issue

In many actor systems (most notable Erlang), executors are optimized by having a "next task" slot in each executor queue. Whenever a new `Runnable` is scheduled, the future is first...

`st3` looks to be a fairly promising public crate for implementing `tokio`'s `!Send` local worker queues which eliminate most of the atomic operations when popping from the local queue. Right...

enhancement

Resolves #111. Creates a `StaticExecutor` type under a feature flag and allows constructing it from an `Executor` via `Executor::leak`. Unlike the executor it came from, it's a wrapper around a...

WIP for now, as the current implementation is slow

Fix #32. This PR replaces the fixed-sized local worker queues with st3's implementation. The implementation in the crate itself is largely the same, but st3's implementation should use considerably fewer...

This was originally implemented in #37, but the implementation turned out to be very buggy so I removed it in #61. Still, I think it's an important optimization even for...

A `'static` Executor that has been leaked never has its `Drop` impl called. This may not be uncommon for use cases where an executor is initialized at startup and never...

I was excited to see the addition of `StaticExecutor` and `StaticLocalExecutor` optimizations, and started [async-global-executor#17](https://github.com/async-rs/async-global-executor/pull/17) with the intent to adopt both of them. However, it is unclear from the examples...

based on https://github.com/smol-rs/smol-macros/pull/10#issuecomment-2425229319