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

Task abstraction for building executors

Results 15 async-task issues
Sort by recently updated
recently updated
newest added

Code for reproduce: ```Rust use std::{ cell::RefCell, thread::{self, sleep}, time::{Duration, Instant}, }; use async_task::{Runnable, Task}; use futures::{channel::mpsc, Future, StreamExt}; thread_local! { static RUNNABLE_LIST: RefCell = RefCell::new(Vec::new()); } fn poll_once() ->...

The [`Task::cancel`](https://docs.rs/async-task/3.0.0/async_task/struct.Task.html#method.cancel) API is used to cancel a task through the remote handle. The [`Drop::poll_drop_ready` RFC](https://github.com/rust-lang/rfcs/pull/2958) proposes a mechanism through which async destructors can be added to the language. I'd...

I've been working on a specialized fork of `async_executor` focused on prioritized execution high performance CPU bound tasks for bevy. Thus far I've made a number of optimizations that definitely...

#### The following code is logic in my dynamic call based async-task project. And Here, I didn't let the task reschedule to run, but it didn't seem any problem. *...

## Motivation It is currently possible to use `async_task` with `no_std`, but it requires having `alloc` available because tasks are dynamically allocated. In memory-constrained environments, such as embedded microcontroller devices,...

Ability to create an already completed `Task` with something like `Task::completed(...)`. This would serve as a way to mock asynchronous functionality with synchronous code. My specific use case is an...

In the course of resolving #31, I realized that users may want to associate other things with tasks, like string names, priorities, debugger information, and otherwise. This PR adds a...

In order to make it easier to debug tasks, it should be possible to give tasks names. I was thinking of an API like this: ```rust Task::builder().name("my-task").spawn(async { println!("Hello world!");...

`async-task` contains an optimisation for handling large futures in the definition of [spawn_unchecked](https://github.com/smol-rs/async-task/blob/master/src/runnable.rs#L516). This leads to excessive IR size, as one branch instantiates `RawTask` with Fut and the other does...

The command `cargo test --all-targets --no-default-features` fails like this: ``` 514s error[E0425]: cannot find function `spawn_local` in crate `async_task` 514s --> examples/spawn-local.rs:22:40 514s | 514s 22 | let (runnable, task)...