Avoid copying bitset that's subsequently cleared #15582
Merged
+36
−17
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.
In two instances,
FixedBitSet.ensureCapacity()was called right before the bitset was cleared. This unnecessarily copied the internal array.This PR adds
FixedBitSet.ensureCapacityAndClear()that avoids the copying. This should give a small performance improvement.Also rename
numBitstodesiredBit- the argument didn't specify the number of bits we want to store, but the desired index we wanted to store at. This allowed for a much simpler javadoc that's not self-contradictory.