Meeting C++ 2025 - (Don't) use coroutines for this

Ivan Čukić

On Day 3 at 10:20 (CET/Berlin) in Track B [Opal Room and online]

Coroutines were touted as one of the most important features of C++20, and we had many talks to watch and blog posts to read about how they work internally and how to customize them and implement our own coroutine types for writing structured conurrent code. Since then, the Standard got no asynchronous coroutines, and most effort in the area of 'structured concurrency' went to senders and receivers.

While we don't have asynchronous coroutines in the standard, we did get one synchronous coroutine-based type -- std::generator.

Is that all the coroutines are useful for now?

In this talk, we'll try to move away from concurrency and asynchronous execution mindset when looking at coroutines and move into the "coroutines are just another flow control language feature like branching, loops, functions...".

We will see a few examples showing how coroutines can be used to simplify real-world code even for things other than concurrency and asynchronous execution.

Please login to comment