Re: Any objections to making C++14 the current baseline for Boost support and testing?

From: Christophe B (boost_at_[hidden])
Date: 2022-06-10 13:44:22

Hi,

Would there be an intent to increase the support of new standard libraries by boost libraries? On top of my head, I think first to shared_ptr<> and 
error_code.
Mixing std libraries and their equivalent in boost is most of the time tedious. Concretely, it becomes difficult to integrate components and 
interoperate them when some adopt std::error_code while others must stick boost::system::error_code due to constraints (mainly asio and beast. We 
thought to migrate to the standalone asio, but there is no equivalent for beast). Even if some efforts have been done to convert boost error_code to 
std ones, this is far from ideal.

And as mentioned by Martijn Otto, I would opt also for jumping directly to C++17.

BTW, could you give the list of orphan libraries?

My 2 cents

On 06/05/2022 10: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_at_[hidden]
> https://lists.boost.org/mailman/listinfo.cgi/boost-users