xtonik

I have written [the validation](https://github.com/RoaringBitmap/RoaringBitmap/commit/85c37485f6ace972fd0c8f99a6d03c6c90e3ef5b) according to C version of Roaring bitmaps. Some checks were removed, e.g. it is impossible to have negative capacity as it is derived from array...

I use "Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz" running on Debian 11. One thing is`(char) (c - '0') < 10` vs. `'0'

Yes, you have right - within parser is the change unnoticeable. I have created separate benchmark, which gives me clear results in favour of conditional variant. But this should not...

I have found the reason - there was included "the example of how not to use `isDigit()` at all", it is rolled back by last commit caee9b2 and little difference...

It should be good to remove all dead code sections, not all were removed within #137, there are still many of them in `MappeableBitmapContainer`, it improves significantly code readability and...

Isn't this duplicate to resolved #162?

The issue can be solved by simple [change](https://github.com/RoaringBitmap/RoaringBitmap/commit/1f01f5bc234d17c12f9a9635dd57cd40bbcb4616). In the change for Go version, there are three changes as the commit solves the first, the second is not relevant for...

Is it still requested? I can do that as it is simple task - mix of existing `equals()` in `(Immutable)RoaringArray` and `(Immutable)RoaringBitmap`.

Please rerun the tests, their failure was caused by network error during downloading Gradle.