Jackson Newhouse

I believe https://github.com/RoaringBitmap/roaring/blob/master/serialization_generic.go does not assume endianness, hence the "generic" monicker. I also believe it to be correct, as that was what was being used on arm64 machines until we...

I realized AndAny's issues when I refactored array.ior(run) to potentially return a new run container. At first I thought I had found a bug but because of when those unchecked...

https://github.com/DLTcollab/sse2neon seems like a valuable reference

Unfortunately golang hasn't ported over UMIN and UMAX. I opened an issue on it, but will probably have to figure out the bitwise representation for now.

@lemire, the intersection algorithms use _mm_cmpestrm to compare 2 registers of 8 shorts each, and there isn't an equivalent instruction in arm64, I believe. Have any suggestions? My thoughts are...

I've given this some more thought, and I'm not sure a single method like that is the right approach. If you're trying to do addition with minimal allocation I think...

My general understanding is that the safety of a Bitmap basically operates under Rowlock semantics. Non-mutating reads can happen concurrently, but any updates need exclusive access, as they can corrupt...

I believe this happens because ReadFrom does not actually inspect the contents of the containers at all, instead just passing references to the slices that represent the contents. This allows...

Hi there, thanks for reaching out. I think we'll want to explore this down the line, as long-running streaming applications are a great place to do PGO. That being said,...

We don't have anything planned in the short-term, but with the newly refactored Connection interfaces it should be pretty straightforward. How would you be looking to use Arroyo with these?...