Modern Concurrency: Getting Started

Heads up... You've reached locked video content where the transcript will be shown as obfuscated text.

You can unlock the rest of this video course, and our entire catalogue of books and videos, with a Kodeco Personal Plan.

Unlock now

You finished this course, great work! Your second app gave you a more detailed look at AsyncAwait, AsyncSequence, and MainActor. The top-level asynchronous task gave you another way to call an asynchronous method from a Swift UI view. You learned the async let syntax for grouping asynchronous tasks so they run at the same time. You used a download stream iterator to process async sequence bites. You got more practice canceling tasks, and you even integrated a combined publisher into your app. You're now ready to take on the next course, Modern Concurrency: Beyond the Basics, where you'll work on three different apps. You'll use AsyncStream to streamline creating async sequences. And you'll learn about continuations, a new mechanism for switching between suspended tasks. You'll find it's also handy for bridging existing code. And there are episodes on writing unit tests for AsyncAwait networking. Part two of the next course is all about dynamic concurrency using TaskGroup. Concurrency always raises the problem of mutating shared state. Swift Concurrency solution is the new Actor type. You've already used the MainActor to make sure UI updates happen on the main thread. In the next course, you'll learn how to make your code thread safe with Actor. The next course begins with the Sky app, which pretends to scan satellite imagery of the sky and analyze it for signs of alien life. You'll spend the rest of part one implementing Blabber, a messaging app that lets you chat with friends. You'll add features like a countdown timer and location sharing. Then in part two, you'll implement EmojiArt, an app that lets you browse an online catalog of digital emoji art. To verify that the digital art is authentic, the app reads the feed of current works of art from the server, verifies the digital signature of the images, and only then displays them on screen. You'll use Actors to implement both memory and on-disc caches. See you soon.