Releases: SalvatorePreviti/roaring-node
Releases · SalvatorePreviti/roaring-node
v1.4.1 (CRoaring 0.9.2)
- Fixes and improves typescript types: new interface ReadonlyRoaringBitmap32
- new method RoaringBitmap32::asReadonlyView() that returns a readonly view on the given bitmap, all write methods will throw error if called.
v1.4.0 (CRoaring 0.9.2)
- Upgrade to croaring 0.9.2
- Support for frozen serialization and deserialization formats
- New property isFrozen and new method freeze() to make a bitmap readonly
- toUint32ArrayAsync, serializeAsync
- Better APIs with more options for several methods (maxLength and offset, and output as argument for serialize, serializeAsync, toSet, toArray, toUint32Array ...)
- New functions: rangeIntersects, static addOffset
- New functions: bufferAlignedAlloc, bufferAlignedAllocUnsafe, isBufferAligned, ensureBufferAligned
- Proper and precise use of AdjustAmountOfExternalAllocatedMemory for every memory allocation
- Allocation details function getRoaringUsedMemory and static method getInstancesCount to track how much memory is used by roaring bitmaps and how many instances are active
v1.3.0 (CRoaring 0.8.1)
update roaring, add node 17 and 18
v1.2.0 (CRoaring 0.4.0)
- Update roaring to 0.4.0
- Reduce binary size and loading time by cleaning up and some compiler flags (linux/mac)
- Remove Jest, use Mocha instead
- Compatibility between RoaringBitmap32 and Set, implementation and typescript, so a RoaringBitmap32 can be used as Set.
- Partial mitigation of #37 issue - a call to runOptimize or shrinkToFit will compute the serialized size in bytes of the map and call AdjustAmountOfExternalAllocatedMemory accordingly, call those function when you are finished updating it (or once in a while). Creating a RoaringBitmap32 adds 8192 bytes by default (and removes on destruction).
v1.1.7 - august 2021
- Add support for node 14, 15 and 16
- Update Roaring to version 0.3.3
- Add support to roaring_bitmap_range_uint32_array via the new method rangeUint32Array - thanks to @cigolpl
- Use dynamic CPU dispatch of Roaring 0.3.3 instead of having multiple binaries
- Improves compilation time and binary size
- BREAKING CHANGE: now the "portable" flag in all the serialization and deserialization methods is mandatory, functions will throw an error if not passed.
v1.0.6
- fixed memory leak with static operations (like RoaringBitmap32.andNot(a, b))
- support for NodeJS 13
- memory management improvements
v1.0.5
supports node 12
1.0.4
- Fixes SSE2 detection if supported by CPU but disabled by OS
- Introduces xorMany static function
- Update of CRoaring to v0.2.60
v1.0.3 - croaring 0.2.57
- implementation of rangeCardinality
- optimized removeMany
v1.0.2
Support for Node 11