On Wed, 24 Oct 2018 at 20:31, Niall Douglas via Boost
But we can't just stop investing effort in C++03 maintenance. We have to officially drop C++03 at the Boost level, meaning, refuse to compile Boost with C++03 at all, or make it difficult, or at least make it choose an intelligent default that is never C++03.
As Beman suggested so many years ago now, it's long overdue for a separate Boost v2.x release which is shorn of the backwards compatibility and undermaintained libraries.
I'd make it C++ 17 by default, too, as surveys suggest people are jumping straight from C++ 11 to C++ 17 and not stopping at C++ 14.
+1
People can keep around Boost 1.x with the existing libraries as long as people want it. Let's just break free of the ancient cruft already.
+1
And before anyone asks, it would be on each individual library maintainer to do the work to put their library into Boost 2.x. Which should be 100% cmake, incidentally.
+1 Let's leave Boost 1.x as is, as mixture of 03, 11, 14, etc. Let's revolutionarly reserve make Fosbury's flop reserving - Boost 17.x with `-std=c++17` as minimum - Boost 20.x with `-std=c++20` as minimum ... Best regards, -- Mateusz Loskot, http://mateusz.loskot.net