Skip to content

Releases: RoaringBitmap/roaring

Version 0.9.4

07 Aug 20:25
e6471ed
Compare
Choose a tag to compare

Bug fix release.

  1. In some instances, the Or function could produce erroneous results, see #330 (credit @Crash129)
  2. Our implementation failed to abide by the roaring specification: if one used the FastOr function, one could get good performance, at the expense of memory usage, by producing bitmap containers containing fewer than 4096 entries (see PR #107). We reverted this anomalous behaviour which should result in memory usage in line with the roaring format.

Version 0.9.2

20 Jul 14:05
3676ac2
Compare
Choose a tag to compare

Fix a potential overflow with respect to the frozen format support.

Version 0.9.1

06 Jul 15:20
ff33c3b
Compare
Choose a tag to compare

fix deserialization when size=0xFFFF

credit: @pforemski

Version 0.9.0

05 Jul 13:14
86ac70e
Compare
Choose a tag to compare

Introducing support for the frozen format.

credit: @Oppen

Version 0.8.0

22 Jun 12:41
a6ecb19
Compare
Choose a tag to compare
Merge pull request #321 from RoaringBitmap/issue-320-feature

Added MinMax() function.

Version 0.7.4

15 Jun 15:35
5eef387
Compare
Choose a tag to compare

Fixed an issue with ParOr in roaring64 and fixing support for negative values in BSI.

Credit @guymolinari

Version 0.7.3

08 Jun 22:13
c57a7b2
Compare
Choose a tag to compare

Fix issue with AddOffset

credit: @Oppen

Version 0.7.2

07 Jun 22:49
2feadb1
Compare
Choose a tag to compare

Performance improvments with run containers.
credit: @jacksonrnewhouse

Version 0.7.1

28 May 14:13
Compare
Choose a tag to compare

Patch release to fix a go.sum issue.

Version 0.7.0

28 May 14:08
Compare
Choose a tag to compare
  • updated bitset to new location
  • removed cached cardinality from run containers to make data races less likely