Repository navigation
fix: support pointer key types in hashKey - #84
Open
AdamMagued wants to merge 1 commit into
Open
AdamMagued wants to merge 1 commit into
AdamMagued wants to merge 1 commit into
Conversation
Support reflect.Pointer and reflect.UnsafePointer in setDefaultHasher by hashing the pointer address using word-size xxhash, and update the hashable type constraint to comparable. Fixes cornelk#53
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
In Go, native maps and sync.Map support pointer keys. In cornelk/hashmap, instantiating or hashing maps with pointer keys (*T or unsafe.Pointer) was unsupported because the hashable type constraint only allowed numeric and string types, and setDefaultHasher did not handle reflect.Pointer or reflect.UnsafePointer, causing a panic.
Changes
Fixes #53