C++ 20 (2a) New Features - Coroutine Anatomy

The video tutorial explores the features and limitations of C++ coroutines, highlighting the keywords and standard library constructs they provide. It discusses the lack of defined semantics for coroutines, leaving developers to implement their own. The tutorial explains how functions become coroutines through the use of Co yield or Co await, and details the compiler's handling of Co await, including the creation of boilerplate code. The video concludes with a brief mention of the next topic, generator expressions.

Which of the following is NOT provided by C++ coroutines?

• suspend_always

• Coroutine semantics

• co_await keyword

• coroutine_handle

What is the primary purpose of C++ coroutine facilities?

• To be used directly by application developers

• To serve as a high-level language for coroutines

• To replace traditional function calls

• To be used by library writers for creating abstractions

How does a function become a coroutine in C++?

• By using the co_await or co_yield keywords

• By declaring it with a special coroutine keyword

• By using a coroutine library

• By defining it in a coroutine namespace

What happens when the await_ready function returns true?

• The coroutine is suspended

• The program jumps to the resume point

• The coroutine is terminated

• The program throws an exception

If await_suspend returns a coroutine handle, what is the next step?

• The program returns control to the caller

• The coroutine is suspended indefinitely

• The coroutine is resumed immediately

• The program terminates