salvatorepreviti/roaring-wasm issues and pull requests

#35 - Now that the memory allocation and dispose was refactored, we can get it more similar to the disposable proposal, https://github.com/tc39/proposal-explicit-resource-management

Issue - State: open - Opened by SalvatorePreviti over 1 year ago

#34 - BREAKING: Improve api

Pull Request - State: closed - Opened by SalvatorePreviti over 1 year ago

#33 - Chunked operatios

Pull Request - State: closed - Opened by SalvatorePreviti over 1 year ago

#32 - Iterators

Pull Request - State: closed - Opened by SalvatorePreviti over 1 year ago

#31 - Define a ReadonlyRoaringBitmap32 interface

Issue - State: closed - Opened by SalvatorePreviti over 1 year ago

#30 - Add join methods

Issue - State: closed - Opened by SalvatorePreviti over 1 year ago

#29 - Calling addMany with a big array or iterable copies the whole array to WASM memory. Would be smarter to do this in chunks.

Issue - State: closed - Opened by SalvatorePreviti over 1 year ago - 1 comment

#28 - memory management

Pull Request - State: closed - Opened by SalvatorePreviti over 1 year ago

#27 - Investigate worker threads support and how to share the same WASM and instances between worker threads

Issue - State: open - Opened by SalvatorePreviti over 1 year ago

#26 - Add frozen bitmaps support

Issue - State: open - Opened by SalvatorePreviti over 1 year ago - 1 comment

#25 - Add iterators support

Issue - State: closed - Opened by SalvatorePreviti over 1 year ago - 1 comment

#24 - Refactor how we manage memory and use FinalizationRegistry for garbage collection https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/FinalizationRegistry

Issue - State: closed - Opened by SalvatorePreviti over 1 year ago - 1 comment

#23 - BREAKING: make the APIs more similar to the nodejs version, for example, isEmpty is a boolean property. Release a new major version

Issue - State: closed - Opened by SalvatorePreviti over 1 year ago - 1 comment

#22 - Write a new specialized emitter for JS code from emscripten - is possible to make things more performant and smaller output

Issue - State: open - Opened by SalvatorePreviti over 1 year ago

#21 - Make NEON SIMD instructions work

Issue - State: open - Opened by SalvatorePreviti over 1 year ago - 1 comment

#20 - Add a new benchmarking toolset, possibly in browser using the existing web-app and node

Issue - State: open - Opened by SalvatorePreviti over 1 year ago

#19 - More functions

Pull Request - State: closed - Opened by SalvatorePreviti over 1 year ago

#18 - Enable SIMD

Pull Request - State: closed - Opened by andreas over 1 year ago - 15 comments

#17 - Ranges more methods and arena alloc

Pull Request - State: closed - Opened by SalvatorePreviti over 1 year ago

#16 - Refactor build, support web and browser tests

Pull Request - State: closed - Opened by SalvatorePreviti over 1 year ago

#15 - Simplify by allocating in JS

Pull Request - State: closed - Opened by andreas over 1 year ago - 1 comment

#14 - Big project refactor

Pull Request - State: closed - Opened by SalvatorePreviti over 1 year ago

#13 - Add Actions CI workflow

Pull Request - State: closed - Opened by andreas over 1 year ago - 4 comments

#12 - Fix build

Pull Request - State: closed - Opened by andreas over 1 year ago

#11 - fs not found

Issue - State: closed - Opened by wangsai-silence over 1 year ago - 2 comments

#10 - Avoid writing outside of the allocated memory when serializing a roaring bitmap in portable mode

Pull Request - State: closed - Opened by papandreou almost 2 years ago - 1 comment

#9 - SIGBUS

Issue - State: closed - Opened by dimaqq over 4 years ago - 2 comments

#8 - Implement range_cardinality method

Issue - State: closed - Opened by lemire about 6 years ago - 1 comment

#7 - Adjust optimization level?

Issue - State: closed - Opened by lemire over 6 years ago - 2 comments

Ecosyste.ms: Issues

GitHub / salvatorepreviti/roaring-wasm issues and pull requests

#35 - Now that the memory allocation and dispose was refactored, we can get it more similar to the disposable proposal, https://github.com/tc39/proposal-explicit-resource-management

#34 - BREAKING: Improve api

#33 - Chunked operatios

#32 - Iterators

#31 - Define a ReadonlyRoaringBitmap32 interface

#30 - Add join methods

#29 - Calling addMany with a big array or iterable copies the whole array to WASM memory. Would be smarter to do this in chunks.

#28 - memory management

#27 - Investigate worker threads support and how to share the same WASM and instances between worker threads

#26 - Add frozen bitmaps support

#25 - Add iterators support

#24 - Refactor how we manage memory and use FinalizationRegistry for garbage collection https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/FinalizationRegistry

#23 - BREAKING: make the APIs more similar to the nodejs version, for example, isEmpty is a boolean property. Release a new major version

#22 - Write a new specialized emitter for JS code from emscripten - is possible to make things more performant and smaller output

#21 - Make NEON SIMD instructions work

#20 - Add a new benchmarking toolset, possibly in browser using the existing web-app and node

#19 - More functions

#18 - Enable SIMD

#17 - Ranges more methods and arena alloc

#16 - Refactor build, support web and browser tests

#15 - Simplify by allocating in JS

#14 - Big project refactor

#13 - Add Actions CI workflow

#12 - Fix build

#11 - fs not found

#10 - Avoid writing outside of the allocated memory when serializing a roaring bitmap in portable mode

#9 - SIGBUS

#8 - Implement range_cardinality method

#7 - Adjust optimization level?

#6 - TypeScript error: no-void-expression Expression has type `void`. Put it on its own line as a statement.

#5 - Missing straight or, and, xor, andNot, clone functions

#4 - Adding a code sample (many users find this useful).

#3 - RoaringBitmap32 toString() currently unimplemented?

#2 - RoaringBitmap32 iterators currently unimplemented?

#1 - refactoring