Provide default hasher types to Vacant
and Occupied
entries
#389
+2
−2
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.
For code which may select to use the
std
HashMap
or thehashbrown
HashMap
based on feature or cfg flags, being forced to provide an explicit hash argument toVacantEntry
orOccupiedEntry
structs requires jumping through some hoops. Specifically, thestd
hash_map::*Entry
structs don't take a hasher type argument at all, making the downstream code change the type entirely when switching fromstd
tohashbrown
or back.For simplicity, its nice to have the argument be optional on the
hashbrown
end, which would let the same code compile with either map.