Demonstrate the pointlessness of nextVal(). #1
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
nextVal() does not make sense with Map. It performs a full Map scan every time it is called. Also, it does not support Maps where different keys point to equal values. This new test and its failure demonstrates how nextVal() is incompatible with Maps which have multiple keys pointing to strictly equal values.
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.
nextVal() does not make sense with Map. It performs a full Map scan
every time it is called. Also, it does not support Maps where
different keys point to equal values.
This new test and its failure demonstrates how nextVal() is
incompatible with Maps which have multiple keys pointing to strictly
equal values.