You hate DispatchQueue.main.async { } ? Good news, @MainActor killed it ☠️

[@v_pradeilles]

⚠️ Xcode 13 beta 3 has introduced a breaking change in the async API, we now need to use `Task { }` instead of `async { }`

[@akhterusman2734]

Hu 86

[@clickbaitking6770]

It works like this because UIViewController is annotated with @MainActor, and the async {}/Task {}function inherits the local actor context, which in this case is the MainActor. asyncDetached {} / Task.detached {} however does not inherit the local actor context, which is why you need to mark an await, a suspension point.

[@itsmikeneas]

I really appreciated the video's progression, allowed me to connect all the dots :)

[@damiragadilov4040]

I have for a question regarding the usage of async {} in the viewdidload while awaiting for the asynchronous method getData Why do not use Task {}? Are async better at this stage? Or is it just the preference?

[@v_pradeilles]

Yes you're absolutely right: you should use Task {} 👍 If I remember correctly, async {} was a syntax that was present during the beta period of Swift Concurrency. (which is when this video was released) I don't even think it's available anymore.

[@veyselbozkurt9272]

What a accent. Nice Video. Thank you

[@rikudousenninn]

great videos man! keep going!

[@salmansiddiqui9522]

Can you make a video on asyncDetached and with priority

[@v_pradeilles]

I’m taking good note 📝 (But I'm going to wait for the beta to end, because the API is way to unstable until then 😅)

[@donathmm3881]

Thank You

[@rohitdhawan02]

Thanks