Enforce assign_range()
mandates for sequence containers
#5086
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.
Resolves #5076 by statically asserting the mandates for the sequence containers
deque
,forward_list
,list
, andvector
.basic_string
also defines a functionassign_range()
, but I did not add a static assert to it:basic_string
includes its own specification ofassign_range()
which does not provide for any Mandates ([string.assign]/16). Besides, the standard doesn't listbasic_string
among the sequence containers in [sequence.reqmts]/1, so it appears to me that [sequence.reqmts]/60 doesn't apply directly tobasic_string
.