Members Only: Today's video is available only to members. If you are already a member, you can access your private podcast feed by visiting https://www.pointfree.co/account.

---

"Region-based isolation" expanded the definition of isolation beyond actors to something called "regions." Learn what a region is, how they work, and how they loosened the overly strict sendability rules of Swift 5.

Members Only: Today's video is available only to members. If you are already a member, you can access your private podcast feed by visiting https://www.pointfree.co/account.

---

Swift 6.2 introduced a brand new vision for "approachable concurrency." This includes two new features that make working with async code much easier: nonisolated-nonsending, and actor-isolated conformances. Let's thoroughly explore both topics and see how they improve things.

Members Only: Today's video is available only to members. If you are already a member, you can access your private podcast feed by visiting https://www.pointfree.co/account.

---

We embark on a side quest to explore some of the community misinformation around actors and performance. A common complaint is that actors are slower than locks, and thus another reason to avoid them. Let's explore why these comparisons aren't quite what they seem, and how actors can in fact be _more_ performant than mutexes and locks.

Members Only: Today's video is available only to members. If you are already a member, you can access your private podcast feed by visiting https://www.pointfree.co/account.

---

We explore the concept of "reentrancy" in actors, and how innocently adding `async`-`await` to an actor method can open you up to a world of race conditions. This problem also shows up when we naively communicate between actors, but we can solve things in a non-naive way and make actor communication completely synchronous.

Members Only: Today's video is available only to members. If you are already a member, you can access your private podcast feed by visiting https://www.pointfree.co/account.

---

Using an actor seems to have forced us from a synchronous context to an asynchronous one, but it doesn't have to be this way. We will show how with the proper tools we can squash many `await`s down to a single one, and we will use "serial executors" to better understand how an actor enqueues work behind the scenes.

Members Only: Today's video is available only to members. If you are already a member, you can access your private podcast feed by visiting https://www.pointfree.co/account.

---

After fighting with legacy locking and mutexes let's explore a modern alternative: actors. We will refactor our data race-sensitive class to an actor and see just how simple and flexible its implementation can be, and we will grapple with something it introduces that locking did not: suspension points.

Members Only: Today's video is available only to members. If you are already a member, you can access your private podcast feed by visiting https://www.pointfree.co/account.

---

We explore the most modern locking primitive in Swift: `Mutex`. It has some serious smarts when it comes to protecting nonsendable state across threads in a synchronous manner, but it also has a serious bug that you should be aware of.

Members Only: Today's video is available only to members. If you are already a member, you can access your private podcast feed by visiting https://www.pointfree.co/account.

---

It turns out that isolating state with an `NSLock` is not as straightforward as it seems, and we _still_ have a subtle data race. But Apple actually provides a more modern tool that _does_ help prevent this data race at compile time. Let's take it for a spin and get an understanding of how it works.

Members Only: Today's video is available only to members. If you are already a member, you can access your private podcast feed by visiting https://www.pointfree.co/account.

---

We have a data race on our hands, which is exactly what Swift concurrency is supposed to solve for. Let's figure out how we managed to get into this mess, and then we will get our feet wet with an isolation tool that predates Swift concurrency: locking.

Members Only: Today's video is available only to members. If you are already a member, you can access your private podcast feed by visiting https://www.pointfree.co/account.

---

What _is_ "isolation" in Swift? We define the term based on Swift's open "evolution" process and flesh out an example from the proposal to get an understanding of its purpose, and see how legacy tools can lead to dangerous situations at runtime.