Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(hashed): fix HashMap using === instead of context.eq for get, addEntry and modifyAt #193

Merged
merged 1 commit into from
Dec 9, 2023

Conversation

vitoke
Copy link
Contributor

@vitoke vitoke commented Dec 9, 2023

Fixes #186

HashMap now correctly uses the context.eq instance to compare keys instead of ===.

Copy link

codecov bot commented Dec 9, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (3e19056) 96.98% compared to head (ace8d5b) 96.98%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #193   +/-   ##
=======================================
  Coverage   96.98%   96.98%           
=======================================
  Files         322      322           
  Lines       54758    54758           
  Branches     6444     6445    +1     
=======================================
+ Hits        53106    53108    +2     
+ Misses       1640     1638    -2     
  Partials       12       12           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@vitoke vitoke merged commit c07b87d into main Dec 9, 2023
5 checks passed
@vitoke vitoke deleted the fix/hashmap-forgets-colliding-keys branch December 9, 2023 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

HashMap "forgets" about colliding (?) keys, unlike HashSet
1 participant