# How many async tasks are still alive

**URL:** https://discourse.julialang.org/t/how-many-async-tasks-are-still-alive/22668
**Category:** General Usage
**Tags:** question
**Created:** [April 3, 2019, 1:09am UTC](https://discourse.julialang.org/t/how-many-async-tasks-are-still-alive/22668 "2019-04-03T01:09:14Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![c42f](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/c42f/32/52842_2.png) [@c42f](https://discourse.julialang.org/u/c42f)
#### Post date: [April 3, 2019, 7:00am UTC](https://discourse.julialang.org/t/how-many-async-tasks-are-still-alive/22668/7 "2019-04-03T07:00:43Z")

</div>

Yes I didn’t mean that PR would help you (sorry). Just pointing out that this stuff is still changing quite a bit internally so the details aren’t settled.

Could I ask about your use case which requires getting a list of tasks? There has been [some](https://github.com/JuliaLang/julia/issues/6283) [discussion](https://discourse.julialang.org/t/schedule-considered-harmful/10540/1) of using the emerging ideas of “structured concurrency” (described eg, [here](https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/)) to rework the way that task lifetimes are managed. I wonder if that would help your use case?

---

_[View the full topic](https://discourse.julialang.org/t/how-many-async-tasks-are-still-alive/22668)._