C++ Core Guidelines: std::array and std::vector are your Friends
In 99 % of your use cases for a sequential container, you are outstanding with a std::array or a std::vector. What? If you don’t believe me, read this post.
This author has not written his bio yet.
But we are proud to say that Rainer Grimm contributed 656 entries already.
In 99 % of your use cases for a sequential container, you are outstanding 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 an 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. Ultimately, we will also have faster build times and an easier way to build packages.
Today, I complet the rules of the C++ core guidelines to source files. They are about header files and namespaces.
I have prepared the pdf bundle. To get it is quite simple.
The organization of source files is a topic quite seldom addressed in C++. With C++20, we will get modules, but until then, we should distinguish between our code’s implementation and interface.
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 that looks quite magic the first time you see them. 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.