[container.reqmts] Avoid dependency of size/max_size on distance(begin(), end())
#6826
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
|
I don't like this. "whenever well-defined" suggests that it's OK for standard containers to allow more elements than can be represented by their Why would we want to push that problem onto users, instead of saying implementations aren't allowed to be stupid? |
|
This feels like a semantic change. Previously, there was a requirement that the result of -> not editorial |
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.
c.size()andc.max_size()should be always well-defined, and thus shouldn't be dependent onstd::distance. Related to #6822.