Point-Free Videos

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 conclude our series by exploring the mode of main actor by default. New Xcode projects come with with setting turned on, so it's important to know the ins and outs of working with it, and how it is affected by "sendable" protocols.

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. --- The `sending` keyword has special behavior when applied to closure arguments, as well as `inout` arguments. We will employ our knowledge of "disconnected" and "task-isolated" regions to get an understanding for how they work, why nested closures are problematic, and how a throwback from our second episode can help us grapple with `inout sending`.

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. --- The `sending` parameter is a powerful concurrency tool new to Swift 6 that allows you to precisely specify how non-sendable values can cross isolation boundaries. We will explore how it works in terms of "region-based isolation," and how we can send values into and out of functions as "disconnected" objects that are free to travel across isolation boundaries.

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.