You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Briefly, what does this PR introduce?
This should address the clang-tidy issues on main (and likely soon in a
PR). clang-tidy runs without errors in my local eic-shell test setup
now.
I considered adding the logic to allow the builds to be against a
variable that encodes the C++ standard, but that quickly ran out of hand
(see discussion on doing this for compilers). With one standard every
three years, I think it's reasonable to deal with this as we go. We only
support C++20 now anyway.
### What kind of change does this PR introduce?
- [x] Bug fix (issue #1149)
- [ ] New feature (issue #__)
- [ ] Documentation update
- [ ] Other: __
### Please check if this PR fulfills the following:
- [ ] Tests for the changes have been added
- [ ] Documentation has been added / updated
- [ ] Changes have been communicated to collaborators
### Does this PR introduce breaking changes? What changes might users
need to make to their code?
No.
### Does this PR change default behavior?
No.
Environment: (where does this bug occur, have you tried other environments)
main
for latest released): mainHEAD
for the most recent on git): HEADSteps to reproduce: (give a step by step account of how to trigger the bug)
Expected Result: (what do you expect when you execute the steps above)
There should be no clang-tidy errors on main.
Actual Result: (what do you get when you execute the steps above)
Many errors, mostly due to C++20 concepts used in with
-extra-arg='-std=c++17'
.The text was updated successfully, but these errors were encountered: