You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The java impl contains a ReadOnlyRoaringBitmap that can be backed by a byte buffer. Is there any interest in including a Roaring bitmap that's backed by a borrowed byte slice whose contents are the serialized format? This could be useful for zero-copy deserialization or memory mapped use cases.
The text was updated successfully, but these errors were encountered:
saik0
changed the title
ImmutablerRoaringBitmap
ImmutableRoaringBitmap
Dec 28, 2021
Thank you for your issue. I have done some research related to this area that you can read in the issue RoaringBitmap/RoaringFormatSpec#9. I don't know if we want to introduce a new type that is able to deserialize from a byte slice &[u8] and only point to serialized bytes, a lazy type that can deserialize its parts on demand.
There is a 'frozen format' supported by the C and Go versions. It is like the normal serialized format, but it adds some alignment so that you can just reinterpret the bytes without undefined behaviour (in C/C++).
The java impl contains a
ReadOnlyRoaringBitmap
that can be backed by a byte buffer. Is there any interest in including a Roaring bitmap that's backed by a borrowed byte slice whose contents are the serialized format? This could be useful for zero-copy deserialization or memory mapped use cases.The text was updated successfully, but these errors were encountered: