Bjarne Stroustrup & Tony van Eerd & Herb Sutter

Bjarne Stroustrup: C++20 Generic Programming
Tony van Eerd: Postmodern C++
Herb Sutter: Quantifying Accidental Complexity: An Empirical Look at Teaching and Using C++

Stream will be here: https://www.youtube.com/watch?v=o2V544cHNKE

Recording will be here: https://www.youtube.com/playlist?list=PLcx5OZDrH5tv9Bz9VGYV7fQCUkOTixOVl

——————————————————

Bjarne Stroustrup: C++20 Generic Programming

* C++20 is a major upgrade of C++ with a network of interrelated features that will help everybody. Writing good fast code become simpler.
* This talk focuses on generic programming, especially the use of concepts. Concepts allows a programmer to be explicit about a template’s requirements on its argument and make generic programming essentially like “ordinary” programming with non-generic types and algorithms.
* Type deduction is key to generic programming and compile-time evaluation is a natural consequence of precisely specified generic code.

——————————————————

Tony van Eerd: Postmodern C++

The term "Modern C++" can be traced back to ... Bjarne Stroustrup!
It was popularized by Andrei Alexandrescu's "Modern C++ Design", published in February 2001.
Much has changed since then. Alexandrescu is off 𝗗abbling in various things, Scott Meyers has retired;
C++11 changed the landscape, then C++14, C++17, and now we are at C++20, with more on the way.

Clearly, we are now in the 𝘗𝘰𝘴𝘵𝘮𝘰𝘥𝘦𝘳𝘯 C++ era.

So let's apply postmodernism to programming. YOU WON'T BELIEVE WHAT HAPPENS NEXT:
- How to concentrate on one section of a programme at a time, and test in isolation. QA HATES HIM!
- postmodern introspection?. IT WILL SHOCK YOU.
- you'll NEVER BELIEVE what a postmodern smart ptr LOOKS LIKE!

Although this is a lighthearted talk, it also aims to be insightful.
In fact, the goal is nothing less than to change the way you think a̶b̶o̶u̶t̶ ̶p̶r̶o̶g̶r̶a̶m̶m̶i̶n̶g̶.

——————————————————

Herb Sutter: Quantifying Accidental Complexity: An Empirical Look at Teaching and Using C++

We often hear “C++ is more complex than it needs to be!” and it’s easy to show a series of anecdotes and “gotcha” examples. This talk is different: It’s a progress report on the first attempt I know of to systematically catalog and empirically quantify C++’s unneeded complexity broadly across the entire standard, to answer “by how much? where? how? and why?” backed up with concrete data. In this talk I present this work, and some initial conclusions that can give us guidance on how to understand the sources of C++’s complexity — and even what we might be able to do about it.