I'm not against breaking compatibility with older c++-versions at all, but given that c++-14 has so few new features compared to c++-11 I do think that it may be better to bump the baseline to c++-17 directly.
Whether we should do that _now_ is another matter. IMNSHO c++17 has been out for long enough that you'd expect most people to now have a compiler that can handle it. On Fri, 2022-05-06 at 09:19 +0100, John Maddock via Boost-users wrote: > Pursuant of discussion elsewhere: > > Does anyone have any concrete objections to Boost moving to a C++14 > baseline? > > This would mean: > > * Library authors can drop and remove all support for pre-C++14 > compilers after a suitable deprecation notice in place for say 3 > releases. > > * The community maintenance team can likewise drop pre-C++14 support > from community maintained / orphan libaries. > > * CI tests no longer need report pre-C++14 results. > > * From the next release onward, the boost super-project should > clearly > announce in our release notes, that C++11 and earlier support may no > longer be available from the start of 2023. > > Thoughts? > > Thanks, John Maddock. > > _______________________________________________ > Boost-users mailing list > Boost-users@lists.boost.org > https://lists.boost.org/mailman/listinfo.cgi/boost-users _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users
