-
Notifications
You must be signed in to change notification settings - Fork 154
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
tests: workaround clang bug with parameter pack after default argument
Change-Id: I69a2f9cbd5eddef9501fecc8a5438301d01ed885
- Loading branch information
Showing
1 changed file
with
10 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2b43d67
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.
Why do we want to support clang 10?
2b43d67
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.
That's a fair question :)
The workaround is trivial in this particular case, and it's just test code, so why not? If a more elaborate workaround had been necessary, I probably wouldn't have bothered.
But to be clear: we don't have to support clang 10, this is definitely a "best effort" kind of support. I'm personally treating gcc >= 10 and clang >= 10 as the baseline because they're both ~5yo compilers (both released in H1 2020). Also they're both available out of the box on Ubuntu 20.04 which is still in widespread use. I'm planning/hoping to gradually move to C++20 over the next few months, that may require dropping a few more older compilers.
2b43d67
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.
Obviously it's the maintainers' call for what to support, but my two cents: