Re: [boost] [range] concepts.hpp broken

Thorsten Ottosen wrote:

Single Pass Range:

types:

range_iterator<T>::type range_iterator<const T>::type

You mean range_mutable_iterator is no longer a public interface but a customization point? It seems a rational idea; "NVI" is always better. range_iterator<remove_const<T>::type> might be cumbersome, though. BTW, why not remove range_size<> from RandomAccessConcept, which is utterly useless, and even wrong around iterator range. Regards, -- Shunsuke Sogame