< What’s the difference between await and async let? | How to use continuations to convert completion handlers into async functions > |
Updated for Xcode 15
Swift’s async let
syntax provides short, helpful syntax for running lots of work concurrently, allowing us to wait for them all later on. However, it only works as async let
– it’s not possible to use async var
.
If you think about it, this restriction makes sense. Consider pseudocode like this:
func fetchUsername() async -> String {
// complex networking here
"Taylor Swift"
}
async var username = fetchUsername()
username = "Justin Bieber"
print("Username is \(username)")
That attempts to create a variable asynchronously, then writes to it directly. Have we cancelled the async work? If not, when the async work completes will it overwrite our new value? Do we still need to use await
when reading the value even after we’ve explicitly set it?
This kind of code would create all sorts of confusion, so it’s just not allowed – async let
is our only option.
BUILD THE ULTIMATE PORTFOLIO APP Most Swift tutorials help you solve one specific problem, but in my Ultimate Portfolio App series I show you how to get all the best practices into a single app: architecture, testing, performance, accessibility, localization, project organization, and so much more, all while building a SwiftUI app that works on iOS, macOS and watchOS.
Sponsor Hacking with Swift and reach the world's largest Swift community!
Link copied to your pasteboard.