Currently (Boost 1.69) range_value<T>::type hard-fails to compile if T is not a range type. This is because it unconditionally uses range_iterator<T>::type and that type is missing in that case. Please, make range_value also SFINAE-friendly, i.e. so that it doesn't hard-fail the compilation but rather doesn't define the type type if T is not a range type.
Currently (Boost 1.69)
range_value<T>::typehard-fails to compile ifTis not a range type. This is because it unconditionally usesrange_iterator<T>::typeand that type is missing in that case. Please, makerange_valuealso SFINAE-friendly, i.e. so that it doesn't hard-fail the compilation but rather doesn't define thetypetype ifTis not a range type.