Feature request: intersection, union, and difference with the tail of another bitmap

[tudor]

Feature request: intersection, union, and difference with the tail of another bitmap

[lemire]

I think we could support functions such as...

• roaring_bitmap_and_inplace_range(a, b, start, end)
• roaring_bitmap_andnot_inplace_range(a, b, start, end)
• roaring_bitmap_or_inplace_range(a, b, start, end)
• roaring_bitmap_xor_inplace_range(a, b, start, end)

would be nice too, but that means you have to be able to deal with partial containers at both ends instead of just at the beginning so it's a bit harder to implement

Is it? I suspect that there is a non-trivial fixed cost involved in starting to code this functionality, but the added complexity of handling both ends is probably not nearly 2x. It may take 15% longer, I would estimate. Of course, the result would be far neater.

[lemire]

Right. So it is a non-trivial amount of work, for sure!!! My argument is that once you get started, it is not much more effort to do a symmetrical work.

It can't be done in a minutes, no matter what.

[tudor]

rages in off-by-one errors

[tudor]

Also note that we'd have to implement out-of-place versions as well (at least at the container level), as in-place isn't really in-place for COW bitmaps.