In the introductory section of the Concurrency chapter of "The Swift Programming Language" I read: When an asynchronous function resumes, Swift doesn’t make any guarantee about which thread that function will run on. This surprised me. It seems odd, comparing…
I'm having some compilation warnings using Xcode 14.2/swift 5.7 (future errors in swift 6). I've some async function tests in a unit test target which include some code to process UI changes in the main loop. There are two related…
I have watched Explore structured concurrency in Swift video and other relevant videos / articles / books I was able to find (swift by Sundell, hacking with swift, Ray Renderlich), but all examples there are very trivial - async functions…
I have an ObservableObject class and a SwiftUI view. When a button is tapped, I create a Task and call populate (an async function) from within it. I thought this would execute populate on a background thread but instead the…
Okay so we all know that in traditional concurrency in Swift, if you are performing (for example) a network request inside a class, and in the completion of that request you reference a function that belongs to that class, you…
Say I have this code: class Presenter { var viewToUpdate: UIView! func updateUI() { viewToUpdate.backgroundColor = .red } } class ShinyNewAsyncAwaitClass { func doAsyncAwaitThing() async { // make network call or something } } class OtherClassThatICantUpdateToAsyncAwaitYet { func doOldClosureBasedThing(completion: @escaping…
@MainActor class A {} class VC: UIViewController { let foo: A init() { self.foo = A() // Error: Call to main actor-isolated initializer 'init()' in a synchronous nonisolated context super.init(nibName: nil, bundle: nil) } @MainActor init() { self.foo = A()…