Hi, folks. Central to the overall Swift concurrency effort is the ability to directly express what we call asynchronous functions . An asynchronous function still returns a result or throws an error, but it does so asynchronously — that is, after a long enough potential delay that it's valuable to allow the thread to go on with other work in the meantime. Traditionally this has been expressed with explicit callbacks (often called "completion handlers" in the Apple ecosystem), but that sacri...
