Swift 6.4 Lands at WWDC 2026 With Async defer, anyAppleOS Availability, and a Borrowing Iterable Protocol
Apple's second Swift release of the WWDC 2026 cycle leans on ergonomics and performance: async cleanup in defer, condensed availability syntax, and a for-in protocol that borrows noncopyable elements.
Overview
Apple used its WWDC 2026 developer conference to ship a second Swift release in a single cycle. According to the Apple Developer WWDC26 Swift guide, Swift 6.4 “delivers improvements designed for developers at every level,” pairing a batch of language ergonomics with performance work in the standard library and Foundation. Writing up the session, Dev.to contributor ArshTechPro framed Swift 6.3 and 6.4 as landing together at WWDC 2026 “with a strong theme running through them: less boilerplate, fewer surprises, and more control.”
The release follows Swift 6.3, whose headline feature was the first official Swift SDK for Android. Where 6.3 pushed the language onto a new platform, 6.4 is largely about smoothing the day-to-day friction of writing Swift.
What We Know
Concurrency cleanup gets less fussy
One of the most-requested changes removes a long-standing restriction in defer blocks. As explained in the Apple Developer WWDC26 “What’s new in Swift” session, “the old restriction on calling async functions from a defer block is now gone.” That lets cleanup code that needs to await something run reliably whether a function returns normally or throws.
Swift’s data-race safety model also picks up two refinements. Per the same Apple Developer session, a class that previously needed @unchecked Sendable because of a weak var property can now declare that property as weak let instead, so it is “immutable and doesn’t stop you from using Sendable checking.” And for types that should not be concurrency-safe at all, the session describes a new opt-out: “if a type shouldn’t be Sendable, you can state that explicitly with the new tilde Sendable syntax,” which “doesn’t stop subclasses from being Sendable.” Dev.to summarizes the pair plainly: “You can now mark a class as ~Sendable to opt out, and weak let properties are supported in Sendable types.”
Condensed availability and per-declaration diagnostics
Two ergonomic features target boilerplate that has accumulated as Apple’s platform list grew. The Apple Developer session notes that Swift now lets developers “condense all of those platform names into one: ‘Any Apple OS’.” Dev.to describes anyAppleOS as “a shorthand that covers iOS, macOS, watchOS, tvOS, and visionOS in one shot.” When a single platform needs a different version, the Apple Developer session says developers “can use anyAppleOS to establish the default and then add more specific attributes for the exceptions.”
Compiler warnings get finer-grained control through a new attribute. The Apple Developer session states that “the @diagnose attribute lets you change the behavior of specific warnings inside a particular declaration” — and Dev.to adds that it controls “how the compiler treats specific diagnostics on a per-declaration basis,” rather than forcing a project-wide flag. A smaller cleanup drops required parentheses: the Apple Developer session says that when using some or any with an optional type, “in Swift 6.4, you can simply get rid of those parentheses and the compiler will take that to mean the only thing that really makes sense.”
A for-in loop that borrows instead of copies
The most technically significant addition is a new looping protocol aimed at performance-critical code. According to the Apple Developer session, “in Swift 6.4, for loops support a new Iterable protocol. The Sequence protocol we all know and love works by copying the elements out of the sequence, the Iterable protocol allows the for loop to borrow them instead. This means it works with non-copyable elements, and also that it doesn’t need to perform reference counting.” The session adds that an Iterable retrieves elements “in batches” — the loop “will ask the iterator for a span of elements and go through them one-by-one.”
For lower-level tuning, the Apple Developer session pairs the existing @inline(never) attribute with a counterpart: “in Swift 6.4, there is now a matching @inline(always) attribute which forces the compiler to inline even when the optimizer isn’t sure it’ll be a good idea.”
Foundation, testing, and the build system
Performance work extends into Foundation. The Apple Developer WWDC26 guide lists Foundation improvements with “URL parsing up to 4x faster.” The underlying change, per the Apple Developer session, is that “NSURL and CFURL were unified to a single Swift implementation,” which “makes these types run faster and use less memory.”
Swift Testing gains a bridge to the older framework. The Apple Developer session explains that “in Swift 6.4, XCTest assertion failures are now reported as test issues when called from Swift Testing,” and that “the interoperability also works in the other direction too, Swift Testing APIs, like the #expect macro work when called from an XCTestCase.” Dev.to describes the practical effect as being able to “freely mix XCTest assertions and Swift Testing expectations in the same codebase.”
On tooling, the Apple Developer session confirms that “Swift Build is now the default build system backend for Swift Package Manager, improving the consistency between Swift Package builds and what you see from Xcode.”
Release schedule
The formal release timeline is tracked on the Swift Forums, where the project names Ben Cohen as “the overall release manager for Swift 6.4.” The same announcement states that “on May 4th, 2026 the release/6.4.x branch will be cut from main,” and that “all language and API changes for Swift 6.4 will go through the Swift Evolution process,” with proposals expected to be completed by the branch date.
What We Don’t Know
Apple’s session materials and the Apple Developer guide describe the feature set but do not pin down a final general-availability date for Swift 6.4; the Swift Forums post documents only the May 4, 2026 branch-cut date and the evolution-proposal deadline. The cross-platform reach of features like the Iterable protocol and the Foundation rewrites on non-Apple targets such as Linux and Windows is not quantified in the cited materials.
Analysis
The shape of Swift 6.4 reflects where the language is in its maturity curve. After 6.3 spent its headline energy reaching a new platform with the Android SDK, 6.4 reads as consolidation: most of its marquee changes remove a special case, delete a required keyword or parenthesis, or let an existing pattern work in one more place. The recurring beneficiary is Swift’s ownership and concurrency machinery — weak let, ~Sendable, async defer, and a borrowing Iterable protocol all chip away at the friction of writing data-race-safe, noncopyable code that the language has been steering developers toward for several releases. Whether that translates into measurable adoption gains is something the citable sources do not yet answer.