Christopher Di Bella

I think a strong argument in favour of this proposal is that it ensures that the type and value have the same name, which seems to be an industry standard...

Thanks for your patience @rayhamel. I wanted a bit of time to think over your comments, but I've been very preoccupied recently. I'll get to this as soon as I...

Hi @rayhamel, to jog my memory on this PR (and the next one), your goal here is to add `ostream` support, right?

C++20 has only a fraction of the support for ranges that range-v3 offers (fewer views, zero actions, zero numeric algorithms). I'd like to use what's in the standard library where...

1. One could be importing code from an external source. 2. Views that the compiler is aware of might have opportunities for optimisations that third-party libraries probably can't be offered....

range-v3 could alternatively follow Abseil's approach and adopt what's in the standard library when it's available. ```cpp // example for range/v3/view/filter.hpp #if defined(__cpp_lib_ranges) and __cpp_lib_ranges >= 201911 namespace ranges {...

Another solution is to insert the current top-level `ranges` namespace into a new top-level namespace, such as `range_v3`. Then it'd be easier for folks to "build" their own `ranges` namespace....

C++ Reference has you covered. * [Concepts library](https://en.cppreference.com/w/cpp/concepts) * [Iterators library](https://en.cppreference.com/w/cpp/iterator) (everything marked with C++20) * [Ranges library](https://en.cppreference.com/w/cpp/ranges) * [Algorithms library](https://en.cppreference.com/w/cpp/algorithm) (everything in namespace `std::ranges`)

> In general should I expect to be able to use the range-v3 stuff with ranges from a standard library? No. Standard ranges offer no guarantees for compatibility with other...

> > > @david-bakin : But wasn't the point of all the concept work done during the development of ranges (v3 or std) that you can e.g. write > >...