-
Notifications
You must be signed in to change notification settings - Fork 6
Update standard to c++17 [OI-3403] #545
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this C++20 or LLVM 20?
@peddie llvm20 issues a deprecation warning when building with c++17, and we have "warning as errors" config. I see albatross uses c++14 standard, should I update CMake/Bazel build to c++17? |
threadpool
c++20 compatibility update threadpool
c++17/c++20 compatibility update
branches: | ||
- 'master' | ||
|
||
concurrency: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding a commit to a PR will stop running workflows
}; | ||
|
||
const auto proposed_params = apply(values, get_params); | ||
const auto proposed_params = albatross::apply(values, get_params); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was trying to use std::apply
, which has different arguments
threadpool
c++17/c++20 compatibility update There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems good to me.
threadpool
has c++17/c++20 compatibility issues because result_of is removed with c++20, and was deprecated in c++17.invoke_result
is used instead.Standard is updated to c++17 in albatross, which involves fixing
albatross::apply
calls.