Skip to content

Conversation

@kazutakahirata
Copy link
Contributor

In C++17, we should use "static constexpr bool" instead of
"static const bool" for class-scope constants for for better
compile-time evaluation and checks.

In C++17, we should use "static constexpr bool" instead of
"static const bool" for class-scope constants for for better
compile-time evaluation and checks.
@kazutakahirata kazutakahirata merged commit fb27f4f into llvm:main Oct 26, 2025
12 checks passed
@kazutakahirata kazutakahirata deleted the cleanup_20251026_Support_YAML_doc branch October 26, 2025 20:34
varun-r-mallya pushed a commit to varun-r-mallya/llvm-project that referenced this pull request Oct 27, 2025
In C++17, we should use "static constexpr bool" instead of
"static const bool" for class-scope constants for for better
compile-time evaluation and checks.
dvbuka pushed a commit to dvbuka/llvm-project that referenced this pull request Oct 27, 2025
In C++17, we should use "static constexpr bool" instead of
"static const bool" for class-scope constants for for better
compile-time evaluation and checks.
Lukacma pushed a commit to Lukacma/llvm-project that referenced this pull request Oct 29, 2025
In C++17, we should use "static constexpr bool" instead of
"static const bool" for class-scope constants for for better
compile-time evaluation and checks.
aokblast pushed a commit to aokblast/llvm-project that referenced this pull request Oct 30, 2025
In C++17, we should use "static constexpr bool" instead of
"static const bool" for class-scope constants for for better
compile-time evaluation and checks.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants