To get a trial key
fill out the form below
Team License (a basic version)
Enterprise License (an extended version)
* By clicking this button you agree to our Privacy Policy statement

Request our prices
New License
License Renewal
--Select currency--
USD
EUR
GBP
RUB
* By clicking this button you agree to our Privacy Policy statement

Free PVS-Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

Message submitted.

Your message has been sent. We will email you at


If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

>
>
>
std::common_type

std::common_type

Nov 10 2021

Definition

std::common_type is a trait from the standard library. This trait allows you to pass an arbitrary number of types, processes them, and outputs their common type. std::common_type became first available in the C++11 standard. When obtaining a common type, std::common_type relies upon the conditional operator and does some conversions we'll review below.

Possible implementation

namespace std
{
template <typename ...>
struct common_type;                                      // (1)

template <typename ...Ts>
using common_type_t = typename common_type<Ts...>::type;

template <>
struct common_type<>                                     // (2)
{
};

template <class T>
struct common_type<T>                                    // (3)
{
  using type = std::decay_t<T>;
};

template <class T, class U>
struct common_type<T, U>                                 // (4)
{
  using type = decay_t<decltype( true ? declval< std::decay_t<T> >()
                                      : declval< std::decay_t<U> >() ) >;
};

template <class T, class U, class ...V>
struct common_type<T, U, V...>                           // (5)
{
  using type = typename common_type<typename common_type<T, U>::type,
                                    V...>::type;
};
}

It's worth mentioning that common_type is implemented in the standard library in a similar way. Now let's examine the code above and see what happens there:

  • The primary variadic class template is declared.
  • For an empty list of template arguments, we declare the explicit template specialization that does not contain anything.
  • For one template argument, we declare the partial template specialization that contains this type after the std::decay trait is performed. This trait removes CV-qualifiers, links, adds pointers for functions (function-to-pointer conversion), and converts arrays to pointers (array-to-pointer conversion).
  • For two template arguments, we declare the partial specialization that infers the resulting type based on the type inference rules of the conditional operator, applying the std::decay trait to the passed arguments beforehand.
  • For three or more template arguments, we declare the partial specialization that first retrieves the common type for the first two arguments. It uses the specialization for 2 types to do this. Then it instantiates itself recursively, passing the common type for the first pair of types and the rest of the template parameter pack as template arguments. Overall, common_type<a, b, c, d> is equivalent to common_type<common_type<common_type<a, b>, c>, d>. See an example on C++ Insights.

Helpful links

Popular related articles
The Last Line Effect

Date: May 31 2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…
Static analysis as part of the development process in Unreal Engine

Date: Jun 27 2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…
The Evil within the Comparison Functions

Date: May 19 2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
The way static analyzers fight against false positives, and why they do it

Date: Mar 20 2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: Jul 31 2017

Author: Andrey Karpov

After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors (how many erro…
The Ultimate Question of Programming, Refactoring, and Everything

Date: Apr 14 2016

Author: Andrey Karpov

Yes, you've guessed correctly - the answer is "42". In this article you will find 42 recommendations about coding in C++ that can help a programmer avoid a lot of errors, save time and effort. The au…
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…
PVS-Studio ROI

Date: Jan 30 2019

Author: Andrey Karpov

Occasionally, we're asked a question, what monetary value the company will receive from using PVS-Studio. We decided to draw up a response in the form of an article and provide tables, which will sho…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…

Comments (0)

Next comments
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →
Accept