Point-Free Videos

🔒 We conclude our series by showing how we can share isolation _across_ boundaries. We will abstract our nonisolated core with a protocol so that our isolated shells can _scope_ down to subdomains and subfeatures, all while retaining all the benefits of controlled isolation we have explored over the series.

🔒 We leverage “Nonisolated Core, Isolated Shell” by introducing the `StoreActor`: a `Store`-like object that runs in the background on the cooperative thread pool, maximizing parallelism for tests and whatever you can imagine.

🔒 Modern concurrency tools like `nonisolated(nonsending)` and `Task.immediate` got us closer to our goal, but we still haven't succeeded. We will take a new approach inspired by Gary Bernhardt's "functional core, imperative shell" pattern that we like to call "nonisolated core, isolated shell."

🔒 We have a type that we want to be non-`Sendable`, but in order for it to participate in async code, it seems like we do need _something_ `Sendable`. Let's explore how we achieve this sendability in ComposableArchitecture 1.0, why it's not ideal, and how a few new Swift concurrency tools allow us to get closer to our goal in a better way.