[
https://issues.apache.org/jira/browse/AVRO-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581624#comment-17581624
]
Thiruvalluvan M. G. commented on AVRO-3610:
-------------------------------------------
[~mgrigorov] I think that will be a great improvement.
When we worked on moving Avro to "modern C++" last year, we were conservative
and didn't want to make a big leap from C++TR1 to C++14 or C++17. Now that a
year has passed without much issues, it makes a lot of sense to do it now. Of
the three choices we have (C++14, C++17 and C++20) I guess C++17 is the best
first step because:
* It is widely available
* changes to Avro exploiting C++17 will be incremental. Using C++20's main
features viz. concepts and modules will require a lot of changes. In fact, I
think it makes sense to build a new Avro binding for C++20 from ground up.
Overall, I think it is a great idea to move to C++17.
> [C++] Upgrade from C++ 11 to C++ 17
> -----------------------------------
>
> Key: AVRO-3610
> URL: https://issues.apache.org/jira/browse/AVRO-3610
> Project: Apache Avro
> Issue Type: Improvement
> Components: c++
> Reporter: Martin Tzvetanov Grigorov
> Assignee: Martin Tzvetanov Grigorov
> Priority: Major
> Fix For: 1.12.0
>
>
> Apache Arrow is discussing upgrading C++ from 11 to 17 -
> https://lists.apache.org/thread/9g14n3odhj6kzsgjxr6k6d3q73hg2njr.
> Avro C++ also builds on C++ 11 at the moment.
> Should we also make this upgrade ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
