Swift 6.4: Simplifying Concurrency and Cross-Apple OS Parity

Host: Hey everyone, welcome back to Allur! I’m your host, Alex Chan, and today we are shifting our focus to the mobile side of the tech world—specifically, the Apple ecosystem. Now, if you’ve been writing Swift for a while, you know that the transition to Swift 6 has been... well, it’s been a journey. It’s a huge shift toward safety and structured concurrency. Host: Joining me today is Marcus Thorne. Marcus is a Lead Mobile Engineer at AppFlow and a frequent contributor to the Swift open-source community. He’s spent the last decade building apps that run on basically everything Apple makes—from the Watch on your wrist to the Mac on your desk. Marcus, it is so great to have you here on Allur. Guest: Thanks so much for having me, Alex! It’s a great time to be talking about Swift. We’ve had a few years of "heavy lifting" with the language, especially with the strict concurrency checks, so 6.4 feels a bit like a reward for all that hard work. It’s really about refining the experience for the developer. Host: I love that—a "reward." It definitely feels like we’ve earned it! So, let’s jump into one of the most visible changes. I was looking through the release notes and saw this new syntax: `anyAppleOS`. For anyone who hasn’t seen it yet, it sounds like a dream. Can you tell us what the "before and after" looks like for a developer working on cross-platform apps? Guest: Oh man, the "before" was... it was messy. Imagine you’re building a shared library. You have a function that’s specific to Apple’s APIs, but not necessarily to one specific device. Before 6.4, your code looked like a layer cake of conditional compilation. You’d have `#if os(iOS) || os(macOS) || os(watchOS) || os(tvOS)`... and maybe even `visionOS` now! Host: That is such a relief. It’s like they finally realized we were all just copy-pasting that same string of five OS names everywhere! It makes the ecosystem feel... I don't know, more like a "family" of devices rather than five separate islands. Guest: This is actually a huge "aha!" moment for a lot of people. So, everyone loves the `defer` statement, right? It’s your safety net. You open a file or a connection, and you write a `defer` block immediately so you *know* it’ll close, no matter how the function exits. Host: Actually, that explains a few weird bugs I’ve seen in the past! It’s one of those things where you think you’re doing the right thing with a `Task` inside a `defer`, but you’re actually just creating a race condition. It’s really interesting how Swift is evolving to catch these "logical" gaps in how we handle data. Guest: It’s massive. And the best part is, you get it for free—no code changes required. Host: It’s like the invisible plumbing of the app just got a major upgrade. You don't see the pipes, but the water pressure is way better. Guest: I’d say the vibe is "maturity." We’ve spent the last couple of years dealing with the "breaking" parts of Swift’s evolution—all those strict concurrency warnings that made us want to throw our laptops. Swift 6.4 feels like Apple saying, "Okay, we’ve built the foundation, now let’s make it pleasant to use." Host: I love that. "Respecting the developer's time." That should be the goal for every language update, honestly. Guest: You can find me on Mastodon at @mthorne or over at my blog, codeandcoffee.io. Thanks for having me, Alex! This was a blast. Host: Anytime! And thank you all for tuning into Allur. Whether you’re writing Swift, Go, or PHP, we’re here to help you navigate the ever-changing tech landscape. Don't forget to subscribe and leave us a review if you enjoyed the show. Until next time, I’m Alex Chan, and happy coding!