Hello,
Note the change in the message topic :-) We now have a draft PR up to switch the C++ standard level to C++17. This allows very nice simplifications in the code, especially the use of elegant constructs that can replace some cumbersome uses of std::enable_if, SFINAE and other pain points. https://github.com/apache/arrow/pull/10414 It seems we were finally able to overcome the main platform compatibility (CI) hurdles, though some effort will probably be necessary to squash all regressions in that area. I haven't seen any opposition previously in this thread, so you are really concerned by this, it would be better to speak up quickly, as otherwise we may decide to move forward with the change. Best regards Antoine. On Thu, 27 May 2021 10:03:03 +0200 Antoine Pitrou <anto...@python.org> wrote: > Hello, > > It seems the only two platforms that constrained us to C++11 will not be > supported anymore (those platforms are RTools 3.5 for R packages, and > manylinux1 for Python packages). > > It would be beneficial to bump our C++ requirement to C++14. There is > an issue open listing benefits: > https://issues.apache.org/jira/browse/ARROW-12816 > > An additional benefit is that some useful third-party libraries for us > may or will require C++14, including in their headers. > > Is anyone opposed to doing the switch? Please speak up. > > Best regards > > Antoine. >
