In 99 % of your use-cases for a sequential container, you are totally fine with a std::array or a std::vector. What? If you don't believe me, read this post.

The rules to the C++ standard library are mainly about containers, strings, and iostreams.

 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.

Today, I complete the rules of the C++ core guidelines to source files. They are about header files and namespaces.

The organisation of source files is a topic which is quite seldom addressed in C++. With C++20 we will get modules, but until then we should distinguish between the implementation and the interface of our code.

I have prepared the pdf bundle. To get it is quite simple.

Honestly, many programmers in my classes have issues with the syntactic sugar of lambdas. Desugaring lambdas with C++ Insights helps quite often.

Variadic templates are a C++ feature which looks quite magic the first time you see it. Thanks to C++ Insights, most of the magic disappears. 

Today's post from Andreas is about template instantiation. C++ Insights helps you a lot to get a deeper insight into this automatic process.