# Swift Concurrency Roadmap

**URL:** <https://forums.swift.org/t/swift-concurrency-roadmap/41611>\
**Category:** Discussion\
**Tags:** concurrency\
**Created:** [October 30, 2020, 5:18pm UTC](https://forums.swift.org/t/swift-concurrency-roadmap/41611 "2020-10-30T17:18:01Z")\
**Posts on this page:** 1\
**Showing post:** 187

<div class="post-metadata">

**Author:** ![ambrosia\_florum](https://avatars.discourse-cdn.com/v4/letter/a/8797f3/32.png) [@ambrosia\_florum](https://forums.swift.org/u/ambrosia_florum)\
**Post date:** [January 19, 2021, 8:04pm UTC](https://forums.swift.org/t/swift-concurrency-roadmap/41611/187 "2021-01-19T20:04:40Z")

</div>

> [@ambrosia\_florum](#):
>
> This excerpt is from the [doc](https://github.com/apple/swift-evolution/blob/main/proposals/0296-async-await.md):  
> `Because potential suspension points can only appear at points explicitly marked within an asynchronous function, long computations can still block threads. This might happen when calling an asynchronous function that just does a lot of work, or when encountering a particularly intense computational loop written directly in an asynchronous function. In either case, the thread cannot interleave code while these computations are running, which is usually the right choice for correctness, but can also become a scalability problem` .

Read it, it is written in the proposal. If you have a hard time understanding it that I will explain: **a function that has gotten onto an await point stall until the awaited target has finished its work**.  
Let me emphasize it again:

> [@ambrosia\_florum](#):
>
> long computations can still block threads

It is written in the doc!

* * *

And as a little explanation, I say that:

- parallelism = multithreading & no data dependencies between thread (they use TLS or something similar)
- concurrency = multithreading & data dependencies between threads (they have to coordinate mutation of shared mutable data)

* * *

At this point, you are either scoff me or have no idea what you are talking about. I suggest you first try to work with something like posix threads and semaphores, or atomics and later come here to share your precious opinion.

---

_[View the full topic](https://forums.swift.org/t/swift-concurrency-roadmap/41611)._
