Ragnar Groot Koerkamp

Going to close this as won't fix, since it's really out of scope of the project.

In fact, the `bit_field_vec![width; a; b]` constructor is still confusing, since it's `vec![value; len]` but here it's `bit_field_vec![width; len; value]`.

Yes `width:` sound best to me. `width => ` is also fine. I'd not do `width, ` since that is similar to the `vec!` macro again in an unexpected way.

Thanks!

Thanks! On git `master` it went down by 17 crates, that's good :) Disabling `rayon` doesn't do much though -- it's also a dependency of both `rdst` and `dsi-progress-logger ->...

Yes exactly. Hence why it may be too much overhead.

Also a `.size()` method would be nice, since the current `estimate_size` needs the generic parameters: ```rust let size = EliasFano::::estimate_size(self.offsets.len(), self.sizes.len()); ``` Ideally that `size` would also include the size...

lgtm, if you can merge #51. I suppose I'm not super familiar with the `seq` and `dict` interpretations, so in practice I'd probably just try whichever extention gives me the...