Levent

This is becoming curiously problematic as both C++20 is a reality and range-v3 still rocks. Would a build/install-time namespace customization be useful to keep backwards compatibility while allowing custom top-level...

> But this has more implications to the underlying range-v3 implementation, as some views expect `default_initializable`. can you an example or two? also it should be ok for a view...

>I guess dropping semiregular in favour of copyable would be a good first step Putting the relevant proposals here for reference: - http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1456r1.pdf view = range && enable_view && ~~copyable~~...

> [..] I wonder how this compiles at all. :-/ cause, (un?)fortunately all current views happen to have non-type args with defaults :)

> I don't think there is much I can do about that second issue. a build time config, or that along with a macro RANGE_BOOST_NAMESPACE?

E.g. two simple boxes can not be drawn side-by-side: ``` want have ┌────┐┌────┐ ┌───┬┬───┐ │ ││ │ │ ││ │ └────┘└────┘ └───┴┴───┘ ```

> In fact, at the moment users have to opt out of using TAfGT during installation > of VS and then manually install GTA, and I don't think that many...

sorely lacking in substance indeed. At a minimum, methods on a generic types should be shown along with a few examples.