Fix Hash index split slot ID when reserving a number of slots which are a power of two #3066
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.
E.g.
When reserving 64 slots, numSlotsOfCurrentLevel will be 32 instead of 64, and the nextSplitSlotId will be 32, instead of 0.
This shouldn't cause any issues, but the behaviour wasn't what I was expecting and it does some unnecessary work.
splitSlot
is called it will split slot 32, but entries used the higherLevelHashMask when inserting into it originally, so all the entries get hashed back into the same slot, and then the level will be incremented and nextSplitSlotId will be reset to 0.(Also added a missing include that's necessary with newer versions of gcc because
<string>
no longer implicitly includes it)