In my last post C++20: Two Extremes and the Rescue with Concepts, I gave the first motivation for concepts. Concepts put semantic constraints on template parameters. Today, I present different use-cases for concepts in a compact form.

I finished my overview of C++20 in the last post. Now, its time to dive into the details. What can be a better starting point for our journey than concepts?

This post concludes my overview of C++20. Today's post is about the concurrency features in the next C++ standard.

My last post "C++20: The Core Language" presented the new features of the C++20 core language. Today, I continue my journey with an overview of the C++20 library.

My last post C++20: The Big Four started with an overview of concepts, ranges, coroutines, and modules. Of course, C++20 has more to offer. Today, let's continue my overview of the core language.

This post presents you the big four: concepts, ranges, coroutines, and modules.

C++20 will be the next big C++ standard after C++11. As C++11 did it, C++20 will change the way we program modern C++. This change is, in particular, true for Ranges, Coroutines, Concepts, and Modules. To understand this next big step in the evolution of C++, let me put it in this post in the historical context of C++ standards.

 My last post gave you the introduction to modules in C++20. This post shows, how to use existing modules.

Modules is one of the five prominent features of C++20. Modules will overcome the restrictions of header files. They promise a lot. For example, the separation of header and source files becomes as obsolete as the preprocessor. In the end, we will also have faster build times and an easier way to build packages.