You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by Antoine Pitrou <an...@python.org> on 2022/08/29 09:20:13 UTC
[RESULT][VOTE] C++: switch to C++17
Hello,
With 5 binding +1 votes, 7 non-binding +1 votes, and no -1 vote, the
vote has passed.
The next steps will be conceptually as follows:
- require C++17 instead of C++11 in the build configuration(s)
- remove pre-C++17 compatibility measures in the codebase
- start using C++17 idioms and features where desirable to reduce
clutter and improve maintainability
(there might be more than 3 PRs though :-))
Regards
Antoine.
Le 24/08/2022 à 17:31, Antoine Pitrou a écrit :
>
> Hello,
>
> I would like to propose that the Arrow C++ implementation switch to
> C++17 as its baseline supported version (currently C++11).
>
> The rationale and subsequent discussion can be read in the archives here:
> https://lists.apache.org/thread/9g14n3odhj6kzsgjxr6k6d3q73hg2njr
>
> The exact steps and timeline for switching can be decided later on, but
> this proposal implies that it could happen soon, possibly next week :-)
> ... or, more realistically, in the next Arrow C++ release, 10.0.0.
>
>
> The vote will be open for at least 72 hours.
>
> [ ] +1 Switch to C++17 in the impeding future
> [ ] +0
> [ ] -1 Do not switch to C++17 because...
>
>
> Regards
>
> Antoine.
Re: [RESULT][VOTE] C++: switch to C++17
Posted by Antoine Pitrou <an...@python.org>.
Hi Sasha,
It's tracked at https://issues.apache.org/jira/browse/ARROW-17110
There's an initial PR at https://github.com/apache/arrow/pull/13991
Regards
Antoine.
Le 31/08/2022 à 00:25, Sasha Krassovsky a écrit :
> Hi,
> What kind of timeline did we decide on? Is this something that can be worked on/merged immediately or should we wait until after 10.0 is out?
>
> Sasha Krassovsky
>
>> On Aug 29, 2022, at 2:20 AM, Antoine Pitrou <an...@python.org> wrote:
>>
>>
>> Hello,
>>
>> With 5 binding +1 votes, 7 non-binding +1 votes, and no -1 vote, the vote has passed.
>>
>> The next steps will be conceptually as follows:
>> - require C++17 instead of C++11 in the build configuration(s)
>> - remove pre-C++17 compatibility measures in the codebase
>> - start using C++17 idioms and features where desirable to reduce clutter and improve maintainability
>>
>> (there might be more than 3 PRs though :-))
>>
>> Regards
>>
>> Antoine.
>>
>>
>>
>> Le 24/08/2022 à 17:31, Antoine Pitrou a écrit :
>>> Hello,
>>> I would like to propose that the Arrow C++ implementation switch to
>>> C++17 as its baseline supported version (currently C++11).
>>> The rationale and subsequent discussion can be read in the archives here:
>>> https://lists.apache.org/thread/9g14n3odhj6kzsgjxr6k6d3q73hg2njr
>>> The exact steps and timeline for switching can be decided later on, but
>>> this proposal implies that it could happen soon, possibly next week :-)
>>> ... or, more realistically, in the next Arrow C++ release, 10.0.0.
>>> The vote will be open for at least 72 hours.
>>> [ ] +1 Switch to C++17 in the impeding future
>>> [ ] +0
>>> [ ] -1 Do not switch to C++17 because...
>>> Regards
>>> Antoine.
>
Re: [RESULT][VOTE] C++: switch to C++17
Posted by Sasha Krassovsky <kr...@gmail.com>.
Hi,
What kind of timeline did we decide on? Is this something that can be worked on/merged immediately or should we wait until after 10.0 is out?
Sasha Krassovsky
> On Aug 29, 2022, at 2:20 AM, Antoine Pitrou <an...@python.org> wrote:
>
>
> Hello,
>
> With 5 binding +1 votes, 7 non-binding +1 votes, and no -1 vote, the vote has passed.
>
> The next steps will be conceptually as follows:
> - require C++17 instead of C++11 in the build configuration(s)
> - remove pre-C++17 compatibility measures in the codebase
> - start using C++17 idioms and features where desirable to reduce clutter and improve maintainability
>
> (there might be more than 3 PRs though :-))
>
> Regards
>
> Antoine.
>
>
>
> Le 24/08/2022 à 17:31, Antoine Pitrou a écrit :
>> Hello,
>> I would like to propose that the Arrow C++ implementation switch to
>> C++17 as its baseline supported version (currently C++11).
>> The rationale and subsequent discussion can be read in the archives here:
>> https://lists.apache.org/thread/9g14n3odhj6kzsgjxr6k6d3q73hg2njr
>> The exact steps and timeline for switching can be decided later on, but
>> this proposal implies that it could happen soon, possibly next week :-)
>> ... or, more realistically, in the next Arrow C++ release, 10.0.0.
>> The vote will be open for at least 72 hours.
>> [ ] +1 Switch to C++17 in the impeding future
>> [ ] +0
>> [ ] -1 Do not switch to C++17 because...
>> Regards
>> Antoine.