[container.requirements.general] Move exposition-only concept #6193
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
The exposition-only concept container-compatible-range is defined in the subclause for allocator-aware containers, that does not actually use it. This requirement is used throughout the subclause for a variety of contains, so relocate the definition into the leading subclause that provides a key to definitions used throughout the containers subclauses.
|
Ugh, what on earth is it doing there. P1206R7 said to add it to [container.requirements.general] but then showed the context from [container.alloc.reqmts] so of course the editors did what they were asked to and put it in [container.alloc.reqmts]. |
jwakely
approved these changes
Mar 21, 2023
jensmaurer
approved these changes
Mar 21, 2023
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 exposition-only concept container-compatible-range is defined in the subclause for allocator-aware containers, that does not actually use it. This requirement is used throughout the subclause for a variety of containers, so relocate the definition into the leading subclause that provides a key to definitions used throughout the containers subclauses.