enable_if compilation question void = nullptr

Stack Overflow Asked by notaorb on August 25, 2020

Does anyone know why assigning type* = 0 doesn’t work, while type* = nullptr does? In both cases typedef void type. Thanks

#include <type_traits>
#include <iostream>

template <class T,
      typename std::enable_if<std::is_integral<T>::value>::type* = 0>
void do_stuff(T& t) {
    std::cout << "do_stuff integraln";

#if 0 // works
template <class T,
      typename std::enable_if<std::is_integral<T>::value>::type* = nullptr>
void do_stuff(T& t) {
    std::cout << "do_stuff integraln";

struct S {};
int main(int argc, char *argv[])
    int i = 1;
    return 0;


clang++ -pedantic -Wall -std=c++11 && ./a.out error: no matching function for call to 'do_stuff'
    ^~~~~~~~ note: candidate template ignored: substitution failure
      [with T = int]: null non-type template argument must be cast to template
      parameter type 'typename
      std::enable_if<std::is_integral<int>::value>::type *' (aka 'void *')
void do_stuff(T& t) {
1 error generated.

2 Answers

Technically speaking, this is because a non-type template argument must be a "converted constant expression" of the parameter type. This means that the argument itself must be a constant expression, and its conversion to the required parameter type must use only the conversions specified in [expr.const]/4.

According to [expr.const]/4, null pointer conversions are only allowed from std::nullptr_t. In other words, the conversion from 0 to a null pointer value is not allowed as part of the implicit conversion sequence in a converted constant expression.

Yet it's perfectly legitimate to specify static_cast<T*>(0) as a template argument to a non-type template parameter of type T*. In other words, a null pointer conversion from 0 is allowed as part of a constant expression. It's only when the conversion is done at a certain point---after computing the argument and while converting the argument type to the parameter type---that the standard forbids it.

I have no idea about the rationale for this rule.

Correct answer by Brian on August 25, 2020

** nullptr and 0 are not the same. **

For a very clear explanation please see the following:

@brian has provided a very good technical answer, but I felt it necessary to add this answer since we should no longer be trying to use 0 for pointer values.

Answered by Geoff on August 25, 2020

Add your own answers!

Related Questions

How to override CSS class over input[type]?

2  Asked on December 25, 2021 by johnnyd


Remove NAs from nested list data frame

2  Asked on December 25, 2021


Bulma + Vuetify can’t access scss variables with Vuejs

1  Asked on December 25, 2021 by fabio-paitra


Liberty activate @MessageDriven

2  Asked on December 25, 2021 by mah454


Traefik 2 Gateway Timeout

1  Asked on December 25, 2021 by casey-daniel


Make TabItems Added Through C# Code Resize Automatically

2  Asked on December 25, 2021 by bradley-a


Api platform handling fille uploads

2  Asked on December 25, 2021 by andrey-kryukov


iTerm2: How to expand split pane temporarily?

3  Asked on December 25, 2021 by pratik-khadloya


Ask a Question

Get help from others!

© 2022 All rights reserved. Sites we Love: PCI Database, MenuIva, UKBizDB, Menu Kuliner, Sharing RPP