24
#include <type_traits>

struct A{};
struct B{};

template <typename T>
struct Foo
{
    typename std::enable_if<std::is_same<T, A>::value>::type
    bar()
    {}

    typename std::enable_if<std::is_same<T, B>::value>::type
    bar()
    {}
};

Error message:

14:5: error: 'typename std::enable_if<std::is_same<T, B>::value>::type Foo<T>::bar()' cannot be overloaded 10:5: 
error: with 'typename std::enable_if<std::is_same<T, A>::value>::type Foo<T>::bar()'

Source on cpp.sh. I thought both typename std::enable_if<std::is_same<T,?>::value>::type could not be valid at the same time.

Edit

For posterity here is my edit based on @KerrekSB's answer -- SFINAE only works for deduced template arguments

#include <type_traits>

struct A{};
struct B{};

template<typename T>
struct Foo
{
    template<typename U = T>
    typename std::enable_if<std::is_same<U,A>::value>::type
    bar()
    {
    }

    template<typename U = T>
    typename std::enable_if<std::is_same<U,B>::value>::type
    bar()
    {
    }
};

int main()
{
};
Olumide
  • 5,397
  • 10
  • 55
  • 104

1 Answers1

27

SFINAE only works for deduced template arguments, i.e. for function templates. In your case, both templates are unconditionally instantiated, and the instantiation fails.

The following variant works:

struct Foo
{
    template <typename T>
    typename std::enable_if<std::is_same<T, A>::value>::type bar(T) {}

    // ... (further similar overloads) ...
};

Now Foo()(x) causes at most one of the overloads to be instantiated, since argument substitution fails in all the other ones.

If you want to stick with your original structure, use explicit class template specialization:

template <typename> struct Foo;

template <> struct Foo<A> { void bar() {} };
template <> struct Foo<B> { void bar() {} };
Kerrek SB
  • 464,522
  • 92
  • 875
  • 1,084
  • 2
    *SFINAE only works for deduced template arguments* ... That's the key!!!!! Thanks bunch @Kerrek. BTW, my original post is MWE. – Olumide Jun 20 '15 at 11:15
  • 3
    @Olumide: Yes, only substitution failures that result from deduction are not errors. Explicitly requested substitutions do fail as a hard error. (An MFE is enough for this case!) – Kerrek SB Jun 20 '15 at 11:16
  • Is there a way have an overloaded constructor like this? – Brent Jun 01 '17 at 22:52