{"id":5793,"date":"2019-10-17T20:54:11","date_gmt":"2019-10-17T20:54:11","guid":{"rendered":"https:\/\/www.modernescpp.com\/index.php\/c-20-an-overview\/"},"modified":"2019-10-17T20:54:11","modified_gmt":"2019-10-17T20:54:11","slug":"c-20-an-overview","status":"publish","type":"post","link":"https:\/\/www.modernescpp.com\/index.php\/c-20-an-overview\/","title":{"rendered":"The Next Big Thing: C++20"},"content":{"rendered":"

C++20 will be the next big C++ standard after C++11. As C++11 did, C++20 will change the way we program modern C++. This change is particularly 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.<\/p>\n

<\/p>\n

\"TimelineCpp\"<\/p>\n

<\/span>The C++ Standards<\/span><\/h3>\n
 <\/div>\n
C++ is about 40 years old. What happened in the last years? Here is a simplified answer which emphasizes C++20.<\/p>\n

<\/span>C++98<\/span><\/h3>\n

At the end of the 80ths, Bjarne Stroustrup and Margaret A. Ellis <\/span>wrote their famous book Annotated C++ Reference Manual <\/a>(ARM). These books served two purposes. First, there were many independent C++ implementations. ARM defined, therefore, the functionality of C++. Second, ARM was the base for the first C++ standard: C++98 (ISO\/IEC 14882). C++98 had a few important features: templates, the standard template library (STL) with its containers and algorithms, strings, and IO streams.<\/p>\n

<\/span>C++03<\/span><\/h3>\n

With C++03 (14882:2003), C++98 got a technical correction that is so small that there is no place on my timeline. In the community, C++03, which includes C++98, is called legacy C++. <\/p>\n

<\/span>TR1<\/span><\/h3>\n

In 2005 something exciting happened. The so-called technical report 1 (TR1; ) was published. TR1 was a big step toward C++11 and, therefore, toward Modern C++. TR1 (TR 19768) is based on the boost project<\/a> founded by members of the C++ standardization committee. TR1 has 13 libraries that should become part of the next C++ standard. For example, the library to the regular expression library, the random number library, smart pointers such as std::shared_ptr<\/span>, and hashtables. Only the so-called special mathematic functions had to wait until C++17.<\/p>\n

<\/span>C++11<\/span><\/h3>\n

C++11 stands for the next C++ standard, but we call it Modern C++. This name also holds for C++14 and C++17. C++11 has many features which fundamentally changed the way we program C++.  For example, C++11 brought the components of the TR1, but also move-semantic, perfect forwarding, variadic templates, or constexpr.<\/span> But this is not all. With C++11, we got a memory model as the fundamental threading base and a threading API. If you are curious, here are my post on the memory model<\/a> and multithreading<\/a> in general.<\/p>\n

<\/span>C++14<\/span><\/h3>\n

C++14 is a small C++ standard. It brought read-writer locks, generalized lambdas, and generalized constexpr functions.<\/p>\n

<\/span>C++17<\/span><\/h3>\n

C++17 is neither big nor small. It has two outstanding features: the parallel STL and the standardized filesystem. About 80 algorithms of the STL can be executed with a so-called execution policy. This means a call std::sort(std::execute::par, vec.begin(), vec.end())<\/span> is a hint for the C++ implementation to sort the container vec in a parallel way. Additionally, you can specify that the sort should be done sequentially (std::execution::seq<\/span>) or vectorized (std::execution::par_unseq<\/span>). As for C++11, boost was also highly influential for C++17. We got the filesystem from boost and the three new data types: std::optional<\/span>, std::variant<\/span>,<\/span> and std::any<\/span>. <\/span>Here are my posts to C++17<\/a>.
<\/span><\/p>\n

<\/span>C++20<\/span><\/h3>\n

C++20 will change the way we program C++ as fundamentally as C++11. This holds, in particular, for the big four: Ranges, Coroutines, Concepts, and Modules. A half year ago, I would write the big five, but contracts were removed in the standardization meeting this year in Cologne. A contract specifies in a precise and checkable way interfaces for software components. My post, C++ Core Guidelines: A Short Detour to Contracts in C++20<\/a>, gives you more details. I should not write about the past. Here is the bright shining, upcoming future.<\/p>\n

The new ranges library enables it to express algorithms directly on the container, compose the algorithm with the pipe symbol and apply them to infinite data streams.<\/p>\n

Thanks to Coroutines, asynchronous programming in C++ may become mainstream. Coroutines are the base for cooperative tasks, event loops, infinite data streams, or pipelines.<\/p>\n

Concepts will change the way we think and program templates. They are semantic categories for valid template arguments. They enable you to express your intention directly in the type of system. If something goes wrong, you will get a short error message.<\/p>\n

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. Ultimately, we will also have faster build times and an easier way to build packages.<\/p>\n

But this by far not all. Here are a few additional highlights:<\/p>\n