< What’s the difference between await and async let? | How to use continuations to convert completion handlers into async functions > |
Updated for Xcode 14.2
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.
SPONSORED Play is the first native iOS design tool created for designers and engineers. You can install Play for iOS and iPad today and sign up to check out the Beta of our macOS app with SwiftUI code export. We're also hiring engineers!
Sponsor Hacking with Swift and reach the world's largest Swift community!
Link copied to your pasteboard.