CppCon 2017: Anthony Williams “Concurrency, Parallelism and Coroutines”

—
—
C++17 is adding parallel overloads of most of the Standard Library algorithms. There is a TS for Concurrency in C++ already published, and a TS for Coroutines in C++ and a second TS for Concurrency in C++ in the works.

What does all this mean for programmers? How are they all related? How do coroutines help with parallelism?

This session will attempt to answer these questions and more. We will look at the implementation of parallel algorithms, and how continuations, coroutines and work-stealing fit together. We will also look at how this meshes with the Grand Unified Executors Proposal, and how you will be able to take advantage of all this as an application developer.
—
Anthony Williams: Just Software Solutions Ltd

Anthony Williams is the author of C++ Concurrency in Action.
—

*-----*
*-----*

[MagnificentImbecil]

This is one of the most knowledgeable persons in the C++ industry. We can see the answers he gives to the audience.

Also, the passion and effort he puts in explaining things are out-of-this-world. If he could give a pint of blood in order to place the knowledge in our heads, he would.

[iddn]

How do coroutines deal with a slow consumer, what stops the producer filling up RAM with coroutine frames? The fact that futures ultimately block makes them pretty much useless IMO, can they not be given a callback instead?

[JiveDadson]

I don't think future.then() will make it into the standard. What does it accomplish that cannot be done better with a co-routine?

[botWi]

This is example of not good talk. He just described the specs, he didn't provide use cases, examples, guidelines, mnemonic rules on how to remember standard.

[JiveDadson]

This is kind of maddening. Give us the names of the #include files. Make it clear whether a slide demonstrates something that a user could write, or it is something that will be in the STL when all is done.