I think there's no need to check for any particular property of iterator_traits
's nested typedefs. It should be enough to check for mere presence of iterator_traits<T>::value_type
(or any other nested typedef, for that matter), because every iterator has one.
#include <type_traits>
#include <iostream>
#include <iterator>
template<typename>
struct void_ {
typedef void type;
};
// remove typename spam below:
template<typename Discard>
using void_t=typename void_<Discard>::type;
template<typename T>
using decay_t=typename std::decay<T>::type;
// stick helper types into details, so the interface
// for is_iterator is cleaner:
namespace details {
template<typename T, typename Enable=void>
sturct is_iterator : is_iterator2<T, Enable> {};
// special case: void* is not an iterator
// but T* specialization would pick it up
// if there weren't the following:
template<typename V>
struct is_iterator<V*, decay_t<V>> : std::false_type {};
// phase 2: SFINAE pass to std::iterator_traits test
// valid in C++14, and in many C++11 compilers, except
// for above void issue:
template<typename, typename Enable = void>
struct is_iterator2 : std::false_type {};
template<typename T>
struct is_iterator2<T,
void_t< typename std::iterator_traits<T>::value_type>
> : std::true_type {};
}
template<typename T>
struct is_iterator : details::is_iterator<T> {};
int main()
{
std::cout
<< is_iterator<int*>::value
<< is_iterator<double>::value;
}
Unfortunately this isn't guaranteed to work in C++11, but C++14 will fix it (thanks to Jonathan Wakely for pointing it out).