itsy_bitsy
Bit containers, sequences, and views for everyone. 🕷️ (by ThePhD)
CRoaring
Roaring bitmaps in C (and C++), with SIMD (AVX2, AVX-512 and NEON) optimizations: used by Apache Doris, ClickHouse, and StarRocks (by RoaringBitmap)
itsy_bitsy | CRoaring | |
---|---|---|
4 | 8 | |
120 | 1,456 | |
- | 1.6% | |
4.1 | 8.9 | |
almost 2 years ago | 5 days ago | |
C++ | C | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
itsy_bitsy
Posts with mentions or reviews of itsy_bitsy.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-07.
-
Bit-vector manipulations in standard C++
No benchmarks though. I saw itsy_bitsy, but other than find and sorting (neither of which I've ever needed), it's not really that much faster than std::bitset.
-
An optimized replacement of the infamous std::vector<🅱️ool>
Another library, to possibly compare against, is: itsy.bitsy.
-
What std::bitset could have been
Are patches you mentioned related to this library https://github.com/ThePhD/itsy_bitsy ?
-
[Suggestion] How to manage a (moderately) large number of bitvectors?
This might do what you need https://github.com/ThePhD/itsy_bitsy . I think it has bitwise ops like bitset but is a dynamic bit vector with decent perf.
CRoaring
Posts with mentions or reviews of CRoaring.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-15.
-
(Don't) crank up the warnings to 11
The PR in question seems to be https://github.com/RoaringBitmap/CRoaring/pull/446
I agree that the GitHub analyses are worse than useless, but I also think it highlights the friction between intrinsics and the program in which they appear. There probably is a better model.
-
Progress in building an 100% rust lang program.
Installation completed the program build successfully!! https://www.reddit.com/r/openbsd/comments/yux513/comment/iwbm72c/?context=3 I configured 2 different files in .cargo (thanx @ivan_linux for https://github.com/RoaringBitmap/CRoaring/pull/412) and .profile ( https://rust-lang.github.io/rust-bindgen/requirements.html#openbsd ) But when I try to start the program unfortunately the node not starting and I get the following errors.
- I will need your help to complete (if possible) a rust lang program installation
- What std::bitset could have been
-
How do Games manage NPC schedules?
I use a fake database paired with compressed bits for flags and integer compression for various other traits. They follow a navigation guide similar to wind for foliage.
-
Help with CFFI, C struct decoding, best practices / portability
I've been using CFFI to access the CRoaring C API to Roaring Bitmaps. It's been pretty easy so far. However I'm not experienced in lisp FFI, and I'm unsure of the way to go about the task of decoding a C structure used for iteration in the C CPI. The structure is as follows: ``` typedef struct roaring_uint32_iterator_s { const roaring_bitmap_t *parent; // owner int32_t container_index; // point to the current container index int32_t in_container_index; // for bitset and array container, this is out // index int32_t run_index; // for run container, this points at the run
-
FFI advice sought
I have a build shared library build of the C API for Roaring Bitmaps and I'm just trying to figure out the right path forward to write a lisp interface to it on sbcl.
-
C Deep
CRoaring - C implementation of Roaring bitmaps. Apache-2.0