You cannot obtain a pointer to member to a type member:
template <typename C> static yes check( decltype(&C::bar) ) ;
The subexpression &C::bar
will only be valid when bar
is a non-type member of C
. But what you need to check is whether it is a type. A minimal change to your template could be:
template <typename C> static yes check( typename C::bar* ) ;
If bar
is a nested type of C
, then that function overload will be a valid candidate (the 0 will be a pointer to whatever C::bar
type is), but if C
does not contain a nested bar
then it will be discarded and the second test will be the only candidate.
There is a different question as of whether the trait is needed at all, since if you use C::bar
in the target template, the template will be discarded automatically for types that don't have that nested type.
EDIT
What I meant is that in your approach you need to create a trait for each and every possible nested type, just to generate a template that does or does not hold a nested type (enable_if
). Let's take a different approach... First we define a general utility to select a type based on a condition, this is not required for this problem, and a simpler template <typename T> void_type { typedef void type; };
would suffice, but the utility template can be useful in other cases:
// General utility: if_<Condition, Then, Else>::type
// Selects 'Then' or 'Else' type based on the value of
// the 'Condition'
template <bool Condition, typename Then, typename Else = void>
struct if_ {
typedef Then type;
};
template <typename Then, typename Else>
struct if_<false, Then, Else > {
typedef Else type;
};
Now se just need to use SFINAE for class template specializations:
template <typename T, typename _ = void>
struct target {
// generic implementation
};
template <typename T>
struct target<T, typename if_<false,typename T::bar>::type> {
// specialization for types holding a nested type `T::bar`
};
Note that the main difference with your approach is the use of an extra intermediate template (the one for which Substitution will Fail --and Is Not An Error) that yields a void
type (on success). This is the reason why the void_type
template above would also work: you just need to use the nested type as argument to a template, and have that fail, you don't really care what the template does, as long as the evaluation is a nested type
(that must be void
) if it succeeds.
In case it is not obvious (it wasn't at first for me) why your approach doesn't work, consider what the compiler needs to do when it encounters target<foo2>
: The first step is finding that there is a template called target
, but that template takes two arguments of which only one was provided. It then looks in the base template (the one that is not specialized) and finds that the second argument can be defaulted to void
. From this point on, it will consider your instantiation to be: target<foo2,void>
(after injecting the defaulted argument). And it will try to match the best specialization. Only specializations for which the second argument is void
will be considered. Your template above will only be able to use the specialized version if T::bar
is void
(you can test that by changing foo2
to: struct foo2 { typedef void bar; }
. Because you don't want the specialization to kick in only when the nested type is void
you need the extra template that will take C::bar
(and thus fail if the type does not contain a nested bar
) but will always yield void
as the nested type.
foo1
is incomplete – is this intentional? – Lonna