Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plan move to C++17 #3121

Open
marcalff opened this issue Nov 4, 2024 · 0 comments
Open

Plan move to C++17 #3121

marcalff opened this issue Nov 4, 2024 · 0 comments
Labels
bug Something isn't working needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@marcalff
Copy link
Member

marcalff commented Nov 4, 2024

According to the Abseil doc:

support for C++14 will be revisited on 2024-12-15:

Per policies:

C++ 14 will be dropped for C++17:

We will drop support for our oldest supported C++ standard when one of the following happens:

    All supported compilers* default to a newer version
    When 10 years pass since the standard's release date
    Example: In 2023, if all supported compilers use C++17 as their default, then we can drop support for C++14. Otherwise, we'll need to wait until 2024, which would be 10 years after C++14 was released.

When abseil no longer supports C++14 and requires C++17, so will gtest, gmock, grpc, overall forcing opentelemetry-cpp to drop C++14 as well.

We need to plan for this

@marcalff marcalff added the bug Something isn't working label Nov 4, 2024
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

1 participant