C++ Core Guidelines: Better Specific or Generic?


Concepts revolutionise the way we think about and use generic programming. They didn't make it in C++11, or C++17 but with C++20 we will get them with high probability.

roads 320371 1280

Before I write about the use of concepts, I want to make a general remark.

Too Specific versus Too Generic

Until C++20 we have in C++ two diametral ways to think about functions or user-defined types (classes). Functions or classes can be defined on specific types or on generic types. In the second case, we call them to function or class templates. What are the downsides of each way?

Too Specific

It's quite a job to define for each specific type a function or a class. To avoid that burden, type conversion comes often to our rescue but is also part of the problem. Let's see what I mean.

Narrowing Conversion

You have a function getInt(int a) that you can invoke with a double. Now, narrowing conversion takes places.

// narrowingConversion.cpp

#include <iostream>

void needInt(int i){
    std::cout << "int: " << i << std::endl;

int main(){
    std::cout << std::endl;
	double d{1.234};
	std::cout << "double: " << d << std::endl;
	std::cout << std::endl;


I assume that is not the behaviour you wanted. You started with a double and ended with an int.


But conversion works also the other way around.

Integral Promotion

You have a user-defined type MyHouse. An instance of MyHouse can be constructed in two ways. When invoked without an argument (1), its attribute family is set to an empty string. This means the house is still empty.  To easily check if the house is empty or full, I implemented a conversion operator to bool (2). Fine or? No!

// conversionOperator.cpp

#include <iostream>
#include <string>

struct MyHouse{
    MyHouse() = default;                            // (1)
    MyHouse(const std::string& fam): family(fam){}
    operator bool(){ return !family.empty(); }      // (2)                         
    std::string family = "";

void needInt(int i){
    std::cout << "int: " << i << std::endl;

int main(){
    std::cout << std::boolalpha << std::endl;
    MyHouse firstHouse;
    if (!firstHouse){                                        
        std::cout << "The firstHouse is still empty." << std::endl;
    MyHouse secondHouse("grimm");                               
    if (secondHouse){
        std::cout << "Family grimm lives in secondHouse." << std::endl;
    std::cout << std::endl;
    needInt(firstHouse);              // (3)                
    needInt(secondHouse);             // (3)
    std::cout << std::endl;


Now, instances of MyHouse can be used, when an int is required. Strange! 


Due to the overloaded operator bool (2), instances of MyHouse can be used as an int and can, therefore, be used in arithmetic expressions: auto res = MyHouse() + 5. This was not my intention! Just for completeness. With C++11 you can declare conversion operators as explicit. Therefore implicit conversions are not allowed.

My strong belief is that because of convenience reasons we need the entire magic of conversions in C/C++ to deal with the fact that functions only accept specific arguments.

Are templates the cure? No!


Rainer D 6 P2 540x540Modernes C++ Mentoring

Stay informed about my mentoring programs.



Subscribe via E-Mail.

Too Generic

Generic functions or classes can be invoked with arbitrary values. If the values do not satisfy the requirements of the function or class, no problem. You will get a compile time error. Fine!

// gcd.cpp

#include <iostream>

template<typename T>
T gcd(T a, T b){
  if( b == 0 ){ return a; }
    return gcd(b, a % b);

int main(){

  std::cout << std::endl;

  std::cout << gcd(100, 10)  << std::endl;
  std::cout << gcd(3.5, 4.0)<< std::endl;
  std::cout << gcd("100", "10") << std::endl;

  std::cout << std::endl;



What is the problem with this error message?


Of course, it is quite long and quite difficult to understand but my crucial concern is a different one. The compilation fails because neither double nor the C-strings supports the % operator. This means the error is due to the failed template instantiation for double and C-string. This is too late and, therefore, really bad. No template instantiation for type double or C-strings should be possible. The requirements for the arguments should be part of the function declaration and not a side-effect of an erroneous template instantiation.

Now concepts come to our rescue.

The Third Way

With concepts, we get something in between. With them, we can define functions or classes which act on semantic categories. Meaning the arguments of functions or classes are either too specific nor too generic but named sets of requirements such as Integral.

What's next?

Sorry for this short post but one week before my multithreading workshop at the CppCon I had neither the time nor in particular the resources (no connectivity in the national parks in Washington state) to write a full post. My next post will be special because I will write about the CppCon. Afterward, I continue my story about generics and in particular about concepts.




Thanks a lot to my Patreon Supporters: Matt Braun, Roman Postanciuc, Tobias Zindl, G Prvulovic, Reinhold Dröge, Abernitzke, Frank Grimm, Sakib, Broeserl, António Pina, Sergey Agafyin, Андрей Бурмистров, Jake, GS, Lawton Shoemake, Animus24, Jozo Leko, John Breland, Venkat Nandam, Jose Francisco, Douglas Tinkham, Kuchlong Kuchlong, Robert Blanch, Truels Wissneth, Kris Kafka, Mario Luoni, Friedrich Huber, lennonli, Pramod Tikare Muralidhara, Peter Ware, Daniel Hufschläger, Alessandro Pezzato, Bob Perry, Satish Vangipuram, Andi Ireland, Richard Ohnemus, Michael Dunsky, Leo Goodstadt, John Wiederhirn, Yacob Cohen-Arazi, Florian Tischler, Robin Furness, Michael Young, Holger Detering, Bernd Mühlhaus, Matthieu Bolt, Stephen Kelley, Kyle Dean, Tusar Palauri, Dmitry Farberov, Juan Dent, George Liao, Daniel Ceperley, Jon T Hess, Stephen Totten, Wolfgang Fütterer, Matthias Grün, Phillip Diekmann, Ben Atakora, Ann Shatoff, Dominik Vošček, and Rob North.


Thanks, in particular, to Jon Hess, Lakshman, Christian Wittenhorst, Sherhy Pyton, Dendi Suhubdy, Sudhakar Belagurusamy, Richard Sargeant, Rusty Fleming, John Nebel, Mipko, Alicja Kaminska, and Slavko Radman.



My special thanks to Embarcadero CBUIDER STUDIO FINAL ICONS 1024 Small


My special thanks to PVS-Studio PVC Logo


My special thanks to Tipi.build tipi.build logo


I'm happy to give online seminars or face-to-face seminars worldwide. Please call me if you have any questions.

Bookable (Online)


Standard Seminars (English/German)

Here is a compilation of my standard seminars. These seminars are only meant to give you a first orientation.

  • C++ - The Core Language
  • C++ - The Standard Library
  • C++ - Compact
  • C++11 and C++14
  • Concurrency with Modern C++
  • Design Pattern and Architectural Pattern with C++
  • Embedded Programming with Modern C++
  • Generic Programming (Templates) with C++


  • Clean Code with Modern C++
  • C++20

Contact Me

Modernes C++,


Tags: Concepts


Stay Informed about my Mentoring


English Books

Course: Modern C++ Concurrency in Practice

Course: C++ Standard Library including C++14 & C++17

Course: Embedded Programming with Modern C++

Course: Generic Programming (Templates)

Course: C++ Fundamentals for Professionals

Interactive Course: The All-in-One Guide to C++20

Subscribe to the newsletter (+ pdf bundle)

All tags

Blog archive

Source Code


Today 1855

Yesterday 4791

Week 1855

Month 191931

All 11673085

Currently are 320 guests and no members online

Kubik-Rubik Joomla! Extensions

Latest comments