Daniel Lemire
Daniel Lemire
@jkeiser BTW this is a real problem. @anonrig got caught and it leads simdjson to issue a TAPE error, which is quite bad. He was understandably upset at simdjson. :-)...
@cppLawyer Thanks. The performance does not need to be a primary concern because we can enable these checks *only* when development checks are activated. It is more important to aim...
@WojciechMula We can lift it but the idea is that you shouldn’t benchmark incorrect code.
RISC-V RVV is still open.
> If I understand correctly, CRoaring supports 64-bit integers in C++ but only 32-bit integers in C. Nope. Please see... https://github.com/RoaringBitmap/CRoaring?tab=readme-ov-file#compressed-64-bit-roaring-bitmaps-c
(It is true that we have independent C++ 64-bit roaring bitmaps... but there is a pure C version too.)
Let me do some work of my own (next few hours).
@Dr-Emann I am re-running a failed test which I do not expect to be related to this PR.