I am reading the SE-0304 (Structured concurrency), and I have come across the following paragraph.
Jobs
The execution of a task can be seen as a succession of periods where the task was running, each of which ends at a suspension point or — finally — at the completion of the task. These periods are called jobs. Jobs are the basic units of schedulable work in the system. They are also the primitive through which asynchronous functions interact with the underlying synchronous world. For the most part, programmers should not have to work directly with jobs unless they are implementing a custom executor.
Could someone explain to me the following bit?
They are also the primitive through which asynchronous functions interact with the underlying synchronous world.
Thank you.