Differentiate nil values from missing keys in Map.Has - #172
Open
AdamMagued wants to merge 1 commit into
Open
AdamMagued wants to merge 1 commit into
AdamMagued wants to merge 1 commit into
Conversation
Previously, Map.Has was implemented as !m.Get(selector).IsNil(). Because Get returns a Value wrapping nil when a key either does not exist or exists with a nil value, Has returned false for keys that were explicitly set to nil or slice indices containing nil elements. This prevented callers from differentiating between non-existent keys and keys mapped to nil/null. Introduce a path traversal helper has that checks for map key presence and array index bounds rather than checking whether the retrieved value is non-nil. Update Map.Has to use has so that existing keys with nil values evaluate to true.
This file contains hidden or 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
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.
Summary
Fixes #131
Previously,
Map.Has(selector)was implemented as!m.Get(selector).IsNil(). BecauseGetreturns aValuecontainingnilwhenever a key does not exist or exists with anilvalue,Hasreturnedfalsefor keys explicitly set tonilor slice indices containingnil. This prevented callers from differentiating between missing keys and keys mapped tonil/null.This change adds a path traversal helper
hasinaccessors.gothat verifies key presence in maps (_, ok := cur[thisSel]) and index boundaries in slices (0 <= index < len(array)).Map.Hasnow delegates tohas, correctly returningtruefor existing keys and indices withnilvalues.Checklist
task testtask lint