One way to get a sense of coroutines is to consider the behavior presented by the async/await design pattern [1], where 'await' suspends the execution of the currently running code and yields control to the 'async' task. (As an adage goes, "async is not asynchronous, and await does not await anything.") Yet another pattern is "promise/future", where the code execution is (or may be) suspended as soon as the code tries to obtain the promised result.

[1] https://learn.microsoft.com/en-us/dotnet/csharp/asynchronous...