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

Fixed bug in Node#find #24

Merged
merged 7 commits into from
Jan 24, 2020
Merged

Fixed bug in Node#find #24

merged 7 commits into from
Jan 24, 2020

Conversation

jonathanGB
Copy link
Contributor

It turns out that find would always return the first entry in a bucket, as longs as the desired entry was found somewhere in the bucket. This can be replicated by reverting the change in lib/node.rs.

At the same time, I added two new constructors of FlurryHashMap, which can take a custom Hasher: the architecture allowed other hashers to be used, but we couldn't actually build any Flurry instances beforehand.

src/lib.rs Outdated Show resolved Hide resolved
src/lib.rs Outdated Show resolved Hide resolved
src/lib.rs Show resolved Hide resolved
@jonhoo
Copy link
Owner

jonhoo commented Jan 24, 2020

Great catch, thanks!

src/lib.rs Outdated Show resolved Hide resolved
src/lib.rs Outdated Show resolved Hide resolved
src/lib.rs Outdated Show resolved Hide resolved
src/lib.rs Outdated Show resolved Hide resolved
src/lib.rs Outdated Show resolved Hide resolved
src/lib.rs Outdated Show resolved Hide resolved
@jonhoo
Copy link
Owner

jonhoo commented Jan 24, 2020

Haha, sorry, I just merged #25, so you'll need to resolve conflicts with master again 😅

@jonhoo jonhoo merged commit 2a5bd25 into jonhoo:master Jan 24, 2020
@jonathanGB jonathanGB deleted the fix-find branch January 24, 2020 19:15
jonhoo pushed a commit that referenced this pull request Nov 19, 2024
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.

2 participants