-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
changes to support newer clang-tidy errors #1898
base: main
Are you sure you want to change the base?
Conversation
the segfault on cxx03_test is a bit of a surprise. i'm debating whether, given we now require c++17 to build the library, it's time to drop the cxx03 stuff and clean everything up anyway. cc @LebedevRI |
so the issue here is that the check for |
i think the right way to do this would be a cxx compiler check in cmake that tries to compile the enum with type, setting a define specifically for that support, then use that in place of the CXX11 check. or we get rid of the cxx03 stuff altogether now we require C++17 :) |
@@ -11,6 +11,14 @@ | |||
#define BENCHMARK_HAS_CXX11 | |||
#endif | |||
|
|||
// This _MSC_VER check should detect VS 2017 v15.3 and newer. | |||
#if __cplusplus >= 201703L || \ |
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 is only defined if the Zc:__cplusplus flag is enabled.
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.
on msvc, yes, which is why we have the rest of the check.
running a straw poll on the discord |
No description provided.