Personally, I always thought that, since C++11, Boost was there to allow
people to be able to use some of the C++11 -> features without needing a
C++11 -> compiler, so it seems a little odd to seemingly abandon those
people who're using it for that purpose.
However, as I've been using C++17 for some time now, it probably doesn't
really affect me.
John
On 06/05/2022 09:19, 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
