# Confused about concurrency problem presented in wwdc24 video

**URL:** <https://forums.swift.org/t/confused-about-concurrency-problem-presented-in-wwdc24-video/74118>\
**Category:** Using Swift\
**Tags:** concurrency\
**Created:** [August 23, 2024, 2:29am UTC](https://forums.swift.org/t/confused-about-concurrency-problem-presented-in-wwdc24-video/74118 "2024-08-23T02:29:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![QuinceyMorris](https://avatars.discourse-cdn.com/v4/letter/q/d26b3c/32.png) [@QuinceyMorris](https://forums.swift.org/u/QuinceyMorris)\
**Post date:** [August 23, 2024, 5:41pm UTC](https://forums.swift.org/t/confused-about-concurrency-problem-presented-in-wwdc24-video/74118/2 "2024-08-23T17:41:27Z")

</div>

No, `nonisolated` just means that it's not isolated to any actor — which of course isn't any kind of explanation.

To understand what's going on, you need to consider an additional piece of information: the function that's being marked `nonisolated` is an `async` function.

A non-isolated async function runs on a special non-actor asynchronous context, and that is similar to the non-main context that concurrent tasks use more generally in Swift. In particular, that's going to involve a non-main thread.

So, it's the combination of `nonisolated` and `async` that "forces" execution off the main thread.

---

_[View the full topic](https://forums.swift.org/t/confused-about-concurrency-problem-presented-in-wwdc24-video/74118)._
