horasal/bitvector_simd

Bitvector implementation with Packed SIMD 2

bitvector_simd's Issues

no len()?

is it just me or is there no way for a user to query for the value of nbits to know the length of a bitvector produced with this api?

from_slice behavior

it seems to me that the from_slice behavior is inconsistent in the presence of repeated indices.

It looks like it assumes that setting from a slice will have at least as many elements as there are in the slice, but if there are repeats then the slice will be set to a larger capacity than is required.

If this tracked nbits separately from the array length of the backing store, then you could still guess at the capacity requirement of the slice by dividing that slice size by 512 (rounded up) and using it as a starting guess at how many BitContainers to put in the backing array, update nbits as you scan through the slice to the highest watermark actually observed, and then trim the backing vec's size back down to fit the data you have.