Due to the  C++ core guidelines "Templates are the backbone of C++’s support for generic programming and class hierarchies the backbone of its support for object-oriented programming. The two language mechanisms can be used effectively in combination, but a few design pitfalls must be avoided." Let me see what this means.

My post for today is just loosely coupled to the rules of the C++ core guidelines because they provide not much content. Inspired by the guidelines, today's post is about a generic isSmaller function.

Template definitions deal with guidelines that are specific to a template implementation. This means, in particular, these rules focus on how a template definition depends on its context.

There is, in particular, one rule left to template interfaces which is quite interesting: T.47: Avoid highly visible unconstrained templates with common names. Admittedly, the rule T47 is often the reason for unexpected behaviour because the wrong function is called.

The topic for today is quite important when you create your type: Regular and SemiRegular types.

Last week I was at two conferences in Berlin: Meeting Embedded and Meeting C++. Here are my impressions from both conferences.

This post is about template interfaces which are due to the C++ core guidelines: "...a critical concept", because a template interface is "a contract between a user and an implementer - and should be carefully designed.".

An interface is a contract between a user and an implementer and should, therefore, be written with great care. This holds also true if you pass an operation as an argument.

Based on my book "The C++ Standard Library" educative.io created an interactive course. You can have it now at a discount.

"C++ Standard Library including C++14 & C++17" is a interactive journey through the current C++ standard Library.

Let me continue with the rules for defining concepts in the guidelines. In this post, the first of the three remaining rules is quite sophisticated.