disambiguate an odr usage requirement in [basic.def.odr] #1243
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.
[basic.def.odr] (6.2.1.3)
Coming from: http://stackoverflow.com/questions/41133290 where T.C. asserted that this should be "not odr-used within the definition of D." Otherwise another entity odr-using the constant could break existing definitions non-odr-use. Alternatively this could read "is not odr-used in all definitions of D" but that language seems more ambiguous.
The example code:
If this appears in a header, it could be broken later (by a strict reading of the current language) if anyone, anywhere odr-uses
CONSTANT