[19-26] Consistent use of _v #783
Merged
Conversation
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
|
Thanks. We'll look at that after the motions have been applied. Expect some rebasing :-) |
AlisdairM
force-pushed
the
consistent_use_of_under_v
branch
from
a2d225b
to
ebf5145
Compare
The library clauses have started to make inconsistent use of the _v variable templates for traits, in preferene to directly querying trait::value. This change set applies that change consistently over all existing wording, where there is a choice of which form might be used. It does not make any changes where the _v variable is not aviable, or is being defined in terms of the corresponding ::value.
AlisdairM
force-pushed
the
consistent_use_of_under_v
branch
from
ebf5145
to
3be939c
Compare
|
rebased off current master (now that all Oulu motions have landed) and force-pushed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The library clauses have started to make inconsistent use of the _v
variable templates for traits, in preferene to directly querying
trait::value. This change set applies that change consistently over
all existing wording, where there is a choice of which form might
be used. It does not make any changes where the _v variable is not
aviable, or is being defined in terms of the corresponding ::value.
This may want a second pass by someone better able to pay attention
to desirable line-breaking.