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/24 15:31:52 UTC

[VOTE] C++: switch to C++17

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: [VOTE] C++: switch to C++17

Posted by Yibo Cai <yi...@arm.com>.
+1 (binding)

On 8/25/22 04:03, Mauricio Vargas Sepúlveda wrote:
> +1
> 
> On 2022-08-24 12:50, Weston Pace wrote:
>> +1 (non-binding)
>>
>> On Wed, Aug 24, 2022 at 9:24 AM Keith Kraus
>> <ke...@voltrondata.com.invalid> wrote:
>>> +1 (non-binding)
>>>
>>> On Wed, Aug 24, 2022 at 12:12 PM David Li <li...@apache.org> wrote:
>>>
>>>> +1 (binding)
>>>>
>>>> On Wed, Aug 24, 2022, at 12:06, Ivan Ogasawara wrote:
>>>>> +1 (non-binding)
>>>>>
>>>>> On Wed, Aug 24, 2022 at 12:00 PM Sasha Krassovsky <
>>>> krassovskysasha@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> ++1 (non-binding)
>>>>>>
>>>>>>> 24 авг. 2022 г., в 08:53, Jacob Wujciak <jacob@voltrondata.com.invalid
>>>>>> написал(а):
>>>>>>> + 1 (non-binding)
>>>>>>>
>>>>>>> Benjamin Kietzman <be...@gmail.com> schrieb am Mi., 24. Aug.
>>>> 2022,
>>>>>>> 17:43:
>>>>>>>
>>>>>>>> +1 (binding)
>>>>>>>>
>>>>>>>> On Wed, Aug 24, 2022, 11:32 Antoine Pitrou <an...@python.org>
>>>> wrote:
>>>>>>>>> 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: [VOTE] C++: switch to C++17

Posted by Mauricio Vargas Sepúlveda <ma...@uc.cl.INVALID>.
+1

On 2022-08-24 12:50, Weston Pace wrote:
> +1 (non-binding)
>
> On Wed, Aug 24, 2022 at 9:24 AM Keith Kraus
> <ke...@voltrondata.com.invalid> wrote:
>> +1 (non-binding)
>>
>> On Wed, Aug 24, 2022 at 12:12 PM David Li <li...@apache.org> wrote:
>>
>>> +1 (binding)
>>>
>>> On Wed, Aug 24, 2022, at 12:06, Ivan Ogasawara wrote:
>>>> +1 (non-binding)
>>>>
>>>> On Wed, Aug 24, 2022 at 12:00 PM Sasha Krassovsky <
>>> krassovskysasha@gmail.com>
>>>> wrote:
>>>>
>>>>> ++1 (non-binding)
>>>>>
>>>>>> 24 авг. 2022 г., в 08:53, Jacob Wujciak <jacob@voltrondata.com.invalid
>>>>> написал(а):
>>>>>> + 1 (non-binding)
>>>>>>
>>>>>> Benjamin Kietzman <be...@gmail.com> schrieb am Mi., 24. Aug.
>>> 2022,
>>>>>> 17:43:
>>>>>>
>>>>>>> +1 (binding)
>>>>>>>
>>>>>>> On Wed, Aug 24, 2022, 11:32 Antoine Pitrou <an...@python.org>
>>> wrote:
>>>>>>>> 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: [VOTE] C++: switch to C++17

Posted by Weston Pace <we...@gmail.com>.
+1 (non-binding)

On Wed, Aug 24, 2022 at 9:24 AM Keith Kraus
<ke...@voltrondata.com.invalid> wrote:
>
> +1 (non-binding)
>
> On Wed, Aug 24, 2022 at 12:12 PM David Li <li...@apache.org> wrote:
>
> > +1 (binding)
> >
> > On Wed, Aug 24, 2022, at 12:06, Ivan Ogasawara wrote:
> > > +1 (non-binding)
> > >
> > > On Wed, Aug 24, 2022 at 12:00 PM Sasha Krassovsky <
> > krassovskysasha@gmail.com>
> > > wrote:
> > >
> > >> ++1 (non-binding)
> > >>
> > >> > 24 авг. 2022 г., в 08:53, Jacob Wujciak <jacob@voltrondata.com.invalid
> > >
> > >> написал(а):
> > >> > + 1 (non-binding)
> > >> >
> > >> > Benjamin Kietzman <be...@gmail.com> schrieb am Mi., 24. Aug.
> > 2022,
> > >> > 17:43:
> > >> >
> > >> >> +1 (binding)
> > >> >>
> > >> >> On Wed, Aug 24, 2022, 11:32 Antoine Pitrou <an...@python.org>
> > wrote:
> > >> >>
> > >> >>> 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: [VOTE] C++: switch to C++17

Posted by Keith Kraus <ke...@voltrondata.com.INVALID>.
+1 (non-binding)

On Wed, Aug 24, 2022 at 12:12 PM David Li <li...@apache.org> wrote:

> +1 (binding)
>
> On Wed, Aug 24, 2022, at 12:06, Ivan Ogasawara wrote:
> > +1 (non-binding)
> >
> > On Wed, Aug 24, 2022 at 12:00 PM Sasha Krassovsky <
> krassovskysasha@gmail.com>
> > wrote:
> >
> >> ++1 (non-binding)
> >>
> >> > 24 авг. 2022 г., в 08:53, Jacob Wujciak <jacob@voltrondata.com.invalid
> >
> >> написал(а):
> >> > + 1 (non-binding)
> >> >
> >> > Benjamin Kietzman <be...@gmail.com> schrieb am Mi., 24. Aug.
> 2022,
> >> > 17:43:
> >> >
> >> >> +1 (binding)
> >> >>
> >> >> On Wed, Aug 24, 2022, 11:32 Antoine Pitrou <an...@python.org>
> wrote:
> >> >>
> >> >>> 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: [VOTE] C++: switch to C++17

Posted by David Li <li...@apache.org>.
+1 (binding)

On Wed, Aug 24, 2022, at 12:06, Ivan Ogasawara wrote:
> +1 (non-binding)
>
> On Wed, Aug 24, 2022 at 12:00 PM Sasha Krassovsky <kr...@gmail.com>
> wrote:
>
>> ++1 (non-binding)
>>
>> > 24 авг. 2022 г., в 08:53, Jacob Wujciak <ja...@voltrondata.com.invalid>
>> написал(а):
>> > + 1 (non-binding)
>> >
>> > Benjamin Kietzman <be...@gmail.com> schrieb am Mi., 24. Aug. 2022,
>> > 17:43:
>> >
>> >> +1 (binding)
>> >>
>> >> On Wed, Aug 24, 2022, 11:32 Antoine Pitrou <an...@python.org> wrote:
>> >>
>> >>> 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: [VOTE] C++: switch to C++17

Posted by Ivan Ogasawara <iv...@gmail.com>.
+1 (non-binding)

On Wed, Aug 24, 2022 at 12:00 PM Sasha Krassovsky <kr...@gmail.com>
wrote:

> ++1 (non-binding)
>
> > 24 авг. 2022 г., в 08:53, Jacob Wujciak <ja...@voltrondata.com.invalid>
> написал(а):
> > + 1 (non-binding)
> >
> > Benjamin Kietzman <be...@gmail.com> schrieb am Mi., 24. Aug. 2022,
> > 17:43:
> >
> >> +1 (binding)
> >>
> >> On Wed, Aug 24, 2022, 11:32 Antoine Pitrou <an...@python.org> wrote:
> >>
> >>> 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: [VOTE] C++: switch to C++17

Posted by Sasha Krassovsky <kr...@gmail.com>.
++1 (non-binding)

> 24 авг. 2022 г., в 08:53, Jacob Wujciak <ja...@voltrondata.com.invalid> написал(а):
> + 1 (non-binding)
> 
> Benjamin Kietzman <be...@gmail.com> schrieb am Mi., 24. Aug. 2022,
> 17:43:
> 
>> +1 (binding)
>> 
>> On Wed, Aug 24, 2022, 11:32 Antoine Pitrou <an...@python.org> wrote:
>> 
>>> 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: [VOTE] C++: switch to C++17

Posted by Jacob Wujciak <ja...@voltrondata.com.INVALID>.
+ 1 (non-binding)

Benjamin Kietzman <be...@gmail.com> schrieb am Mi., 24. Aug. 2022,
17:43:

> +1 (binding)
>
> On Wed, Aug 24, 2022, 11:32 Antoine Pitrou <an...@python.org> wrote:
>
> >
> > 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: [VOTE] C++: switch to C++17

Posted by Benjamin Kietzman <be...@gmail.com>.
+1 (binding)

On Wed, Aug 24, 2022, 11:32 Antoine Pitrou <an...@python.org> wrote:

>
> 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.

[RESULT][VOTE] C++: switch to C++17

Posted by Antoine Pitrou <an...@python.org>.
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: [VOTE] C++: switch to C++17

Posted by Niranda Perera <ni...@gmail.com>.
+1 (non-binding)

On Wed, Aug 24, 2022 at 5:35 PM Micah Kornfield <em...@gmail.com>
wrote:

> +1, I assume this doesn't impact python wheels.
>
> On Wed, Aug 24, 2022 at 2:15 PM Sutou Kouhei <ko...@clear-code.com> wrote:
>
> > +1
> >
> > In <7a...@python.org>
> >   "[VOTE] C++: switch to C++17" on Wed, 24 Aug 2022 17:31:52 +0200,
> >   Antoine Pitrou <an...@python.org> wrote:
> >
> > >
> > > 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.
> >
>


-- 
Niranda Perera
https://niranda.dev/
@n1r44 <https://twitter.com/N1R44>

Re: [VOTE] C++: switch to C++17

Posted by Micah Kornfield <em...@gmail.com>.
+1, I assume this doesn't impact python wheels.

On Wed, Aug 24, 2022 at 2:15 PM Sutou Kouhei <ko...@clear-code.com> wrote:

> +1
>
> In <7a...@python.org>
>   "[VOTE] C++: switch to C++17" on Wed, 24 Aug 2022 17:31:52 +0200,
>   Antoine Pitrou <an...@python.org> wrote:
>
> >
> > 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: [VOTE] C++: switch to C++17

Posted by Sutou Kouhei <ko...@clear-code.com>.
+1

In <7a...@python.org>
  "[VOTE] C++: switch to C++17" on Wed, 24 Aug 2022 17:31:52 +0200,
  Antoine Pitrou <an...@python.org> wrote:

> 
> 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.