The type-traits library has two main goals: correctness and optimization. Today, I write about optimization.

The two main goals of the type-traits library are very convincing: correctness and optimization. Today, I write about correctness.

I finished the last article on the Type-Traits library with the challenge of explaining the std::is_base_of and std::is_convertible functions. Today I'm excited to present the answer from Mr. Helmut Zeisel.

In my last post "The Type-Traits Library: Type Checks" I introduced type checks at compile time with the type-traits library. Today, I write about type comparisons at compile time.

I'm happy to present the seven winners in this post including their answers.

The type-traits library is part of C++11 and supports type checks, type comparisons, and type modifications at compile-time. The library has more than 100 functions but grows with each new C++ standard release. Today, I present the type checks.

First of all, hybrid programming is not an official term. I created it to emphasize a very interesting aspect of templates. The difference between function arguments and template arguments.

I'm happy to announce that I have to offer five vouchers for a digital and two vouchers for a printed issue of Fedor G. Pikus book "The Art of Writing Efficient Programs". The sponsor of these coupons is Packt.

In my last post "Template Metaprogramming - How it All Started", I wrote about the roots of template metaprogramming and presented the hello world of template metaprogramming: calculating the factorial of a number at compile time. In this post, I will write about, how template metaprogramming can be used to modify types at compile time.

Metaprogramming is programming on programs. C++ applies metaprogramming at compile time. It started in C++98 with template metaprogramming, was formalized in C++11 with the type-traits library, and since C++11 has steadily improved. The main driving force is constant expressions. In this post, I want to write about its roots.