boostorg / boostorg/range

Make range_value SFINAE-friendly

Open
#89 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
45
Forks
104
PR merge metrics
No merged PRs in 30d

Description

Currently (Boost 1.69) `range_value::type` hard-fails to compile if `T` is not a range type. This is because it unconditionally uses `range_iterator::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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.