[ARROW-17110] [C++] Move to C++17

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: C++
• External issue URL: https://github.com/apache/arrow/issues/32415
• Assignee: Unassigned
• Reporter: H. Vetinari
• Created: 18/Jul/22 15:07
• Updated: 11/Jan/23 11:48

Description

The upcoming abseil release has dropped support for C++11, so eventually, arrow will have to follow. More details here.

Relatedly, when I tried to switch abseil to a newer C++ version on windows, things apparently broke in arrow CI. This is because the ABI of abseil is sensitive to the C++ standard that's used to compile, and google only supports a homogeneous version to compile all artefacts in a stack. This creates some friction with conda-forge (where the compilers are generally much newer than what arrow might be willing to impose). For now, things seems to have worked out with arrow specifying C++11 while conda-forge moved to C++17 - at least on unix, but windows was not so lucky.

Perhaps people would therefore also be interested in collaborating (or at least commenting on) this issue, which should permit more flexibility by being able to opt into given standard versions also from conda-forge.

Update:

It was voted on the dev ML to move to C++17:

• vote announcement:
  https://lists.apache.org/thread/h9v83rwdl015z2j6s8zwdr1qp4svb5j8
• vote result:
  https://lists.apache.org/thread/dod96gbqtfz7pf096vhlczq6f5hv81z8

Issue Links

• supercedes: ARROW-12816 [C++] C++14 laundry list

Sub-Tasks

• [C++][CI] Mandate C++17 instead of C++11: Resolved
• [C++] Remove pre-C++17 compatibility measures: Closed
• [C++] Adopt C++17 idioms and features for maintainability: Open