Allow null values #154
Merged
Allow null values #154
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
|
@mjpt777 sorry, I forgot to add the new tests to |
snazy
force-pushed
the
allow-null-values
branch
from
03f4ca9
to
d12cc52
Compare
|
Pushed the fix |
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.
This is a variation of #153, that adds the nullability of values to
Object2ObjectHashMap,Int2ObjectHashMap+Long2ObjectHashMap. It's basically identical to the other PR, except that the nullability of the map values is optional viaxyz2NullableObjectHashMap.BiInt2ObjectHashMapalthough allowsnullvalues.Note: this PR does not include the fix for
Object2ObjectHashMap.AbstractIterator.remove(), because it's not implicitly required for this variant of #153.