In this When does a Task get scheduled to the Cooperative Thread Pool? question, I asked why does work inside a Task execute after the function that created it returns. The answer I got was that Task queues up work on the current actor (unless I use .detached) so the current actor must first finish executing before it can run the closure in the Task.
So I was under the impression that Tasks weren’t scheduled asynchronously as something like DispatchQueue.global().async { } would. Rather, they have to wait for the current thread/actor to finish or suspend before they can be submitted anywhere @ktoso