Re: Shall we switch to C++17?

From: Pranam Lashkari (plashkari628_at_[hidden])
Date: 2020-10-24 08:56:11

On Sat, Oct 24, 2020 at 12:50 AM Mateusz Loskot <mateusz_at_[hidden]> wrote:

> Hi,
>
> Recently, there have been some discussions on #boost-gil
> at cpplang.slack.com and in comments on GitHub issues
> about switching GIL to C++17 [1]
>
> TL;TR: Shall we do the switch and when?
>
> We are a small team with limited time and man-power at our
> disposal and we need to spend it wisely and effectively.
> The development comfort and convenience has already been
> improved by the switch to C++11, but there is still more to gain.
>

Agreed.

So, paraphrasing Peter Dimov's sensible suggestion [2] and
> according to the Boost release schedule [3]:
>
> We may declare C++11 support deprecated in Boost 1.75 (December 2020)
> and drop it in Boost release (1.77?) in August 2021.
>
> I think it is a feasible plan with outcome not too distant in the future,
> and GSoC 2021 could allow C++17 too.
>
> I'd like to hear if there are any strong objections.
>

In past, I have objected against using newer standards, but if we think
from the maintenance perspective it makes complete sense to switch to
c++17(if not c++20😂).
I have no objection against switching to c++17.
What needs to be done to deprecate a c++11? is it too much work? do we have
that much time before the release closes(4 days from now)?

Otherwise sounds cool. GIL is on fire 😎

-- 
Thank you,
Pranam Lashkari, https://lpranam.github.io/