Improve performance of set_bits by using copy_from_slice instead of setting individual bytes #2077
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.
Which issue does this PR close?
Closes #2060.
Rationale for this change
Using
copy_from_slice
here reduces the number of bounds checks to one per chunk instead of one per byte.Performance of
boolean_append_packed
improves by about 40% on my laptop.Further improvements should be possible by asserting the bounds once on function entry and then using unsafe
ptr::copy_non_overlapping
in the main loop andget_bit_raw
/set_bit_raw
for the non-aligned parts.What changes are included in this PR?
Are there any user-facing changes?
No