C++11 has user-defined literals for characters, C strings, integers, and floating-point numbers. Integers and floating-point numbers are available in raw and cooked form. Thanks to C++14, we have built-in literals for binary numbers, C++ strings, complex numbers, and time units.
User-defined literals are a unique feature in all mainstream programming languages. They empower you to combine values with units.
Just published: The C++ Standard Library: What every professional C++ programmer should know about the C++ standard library.
The C++ Standard Library: All you have to know as a professional programmer about the C++ library.
The type-traits library empowers you to compare and modify types. All is done at compile time therefore, there is no performance penalty.
Template Metaprogramming is programming at compile time. But what has template metaprogramming in common with the type-traits library? A lot! The type-traits library is pure template metaprogramming, tamed in a library. With this post, my presentation of the type-traits library becomes more structured.
In the post Statically checked I wrote that the functions of the type-traits library are an ideal fit for static_assert. The reason is that static_assert requires a constant expression. The functions of the type-traits library provide a lot of checks which can be performed at compile time. With these posts, I will prove my statement.
static_assert is the tool in modern C++ to make your code safe.
The initialization of variables was unified in C++11. The rule is quite simple. {}-Initialization is always applicable.
Probably the most frequently used feature of C++11 is auto. Thanks to auto, the compiler determines the type of a variable from its initializer. But what is the point of safety-critical software?