Mark constants as _INLINE_VAR constexpr
.
#2792
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@cdacamar explained why he's implementing a new compiler warning:
This warning will complain about non-
inline
constants in headers. We're almost completely consistent about usinginline
in C++17-and-later (or_INLINE_VAR
in potentially-C++14), but Cameron found our inconsistent occurrences:_Size_after_ebco_v
in<xstring>
._INLINE_VAR
.<regex>
, I'm upgradingconst
toconstexpr
.<vector>
, I'm adding a newline to avoid=
alignment, and because typedefs and constants are different.