14 Jun
2019
14 Jun
'19
7:58 a.m.
Hi Neil,
On 13. Jun 2019, at 21:09, Neil Groves via Boost
wrote: Boost.Range v3 fixes the issue by design. V3 is very compelling for new projects.
did you consider to add a note pointing to range-V3 on the frontpage of the docs? https://www.boost.org/doc/libs/develop/libs/range/doc/html/index.html I think it is fair to say: "This library is in maintenance mode, new projects should use library Y." C++ experts like Sutter and Meyers encourage people to explore the Boost libraries and it is great when people follow that advice. Yet, when you explore Boost, you may not know that some library has been superseded by another one maintained outside of Boost, so giving that information is helpful. Best regards, Hans