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 are 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 that 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.

Due to the same history of C and C++, both languages are closely related. Because neither of them is a subset of the other, you have to know a few rules to mix them.

I assume you saw the additional keywords type name or template used before a name in a template. Me too. Honestly, I was quite surprised. Today's post is about dependent names and various template parameters.

I often teach the basics to templates. Templates are special. Therefore, I encounter many misconceptions which cause surprises. Here are a few of them.

Today, I finish the C++ core guidelines rules to templates with a big surprise for many C++ developers. I write about the specialisation of function templates.