Tom Cornebize

I added support for copy on write in Pyroaring (not pushed yet). I was writing some tests and came across this bug. I do not have any use case in...

This test should remain optionnal, right? The users may not want to setup the huge pages just to be able to run the tests. > We could change the permission...

I am not even sure. A first trivial test would be something like that: ```c void test(double expected_time, double epsilon) { struct timeval before, after; gettimeofday(&before, NULL); smpi_execute_benched(expected_time); gettimeofday(&after, NULL);...

Hello, sorry for the delay. I am not super familiar with Cython, so I do not know how to do this. If you want to give it a try, pull...

Thank you for reporting this. I have never taken the time to fix these warning, but I agree that it would be great if pyroaring compiled without them.

Hello, and sorry for the delay. It would be nice to have bindings for `Roaring64Map`. It would be quite a large amount of work though and I do not have...

> Thanks for the response. I don't know if I need 64-bit support after all :-) Alright, I will keep this issue open anyway, in case someone else wants to...

Hello and sorry for the delay. I do not have much time presently, so I cannot implement this feature myself, but I would be glad to review any pull request.

I think my initial thought was to explicitly forbid these operations (see [frozen_bitmap.pxi](https://github.com/Ezibenroc/PyRoaringBitMap/blob/master/pyroaring/frozen_bitmap.pxi)) to avoid any confusion. But you are right that it might be better to respect the "standard"...

Sure, whenever you want! I did not test, but it might be enough to simply remove the methods from the `FrozenBitMap`. I think that if the in-place methods (like `__iand__`)...