Ibraheem Ahmed

@taiki-e which API do you prefer?

That must mean `ReadyToRunQueue` is dropped outside of `FuturesUnordered::drop`. Any idea where?

Could it be https://github.com/rust-lang/futures-rs/blob/b48eb2e9a9485ef7388edc2f177094a27e08e28b/futures-util/src/stream/futures_unordered/task.rs#L46

Hm the stack trace shows: ``` ::drop ```

If `clear` is unsound, then isn't `next` too? ```rust loop { // Safety: &mut self guarantees the mutual exclusion `dequeue` // expects let task = match unsafe { self.ready_to_run_queue.dequeue() }...

`gruvbox-dark` seems to work fine: 

[paperclip](https://github.com/wafflespeanut/paperclip) is a wip OpenAPI tool for Rust. They currently have an [actix-web plugin](https://paperclip.waffles.space/actix-plugin.html) for generating swagger specs. I'm not sure how difficult it would be to create a warp...

@Robert-Cunningham you can write your own `timeout` function that wraps `sleep`: ```rust pub fn timeout(duration: Duration, future: F) -> Timeout where F: Future, { Timeout { future, sleep: sleep(duration), }...

`actix_rt::spawn` also comes up a lot with those new to async. Many jump to `tokio::spawn` instead of using `actix_rt`, and spawning tasks doesn't seem to be covered anywhere in the...

Hi, just getting back to this. I think this use case is served by just creating a second waitgroup within the child task. Cancellation should be propagated in the same...