[array.cons] Fix various wording issues #7054
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.
This PR fixes the following issues:
"The conditions for an aggregate shall be met." does not specify that
array
meets those requirements, and usually we say this explicitly instead of letting the reader figure it out based on the subclause the wording is in. If we reworded this sentence to say "Anarray
is an aggregate" (or something similar), this would just be repeating [array.overview] p2, and we don't need the same normative wording copied and pasted multiple times. Therefore, the first sentence is deleted."Class
array
" is wrong.array
is a class template, not a class. In the rest of [array], we say "anarray
" which is not wrong at least; it can be seen as a shorthand for "a specialization of thearray
class template"."implicit move constructor" is wrong. It's not a defined term, and could reasonably be interpreted to mean "the non-
explicit
move constructor", i.e. converting constructor. That's not what we are trying to say here; we are talking about the implicitly-declared move constructor.I believe the LWG intent is clear enough for all of these issues to be editorial.