Octomind
Same model as opencode, same endpoint, same prices — octomind solved 24/25 to its 19/25, at half the cost. Open-source agent runtime: one binary, any model, runs unattended in CI. Apache 2.0.
A better compressed bitset in Rust
Translation pending
Developer toolsRustGitHub @RoaringBitmapSelf-installOwner unconfirmed
Paste into Claude or ChatGPT for installation instructions suited to your environment.
Have you tried it? One tap is enough. No sign-in needed.
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗This is a Rust port of the Roaring bitmap data structure, initially defined as a Java library and described in Better bitmap performance with Roaring bitmaps.
This crate only supports the current stable version of Rust, patch releases may use new features at any time.
This project uses Clippy, rustfmt, and denies warnings in CI builds. Available via
rustup component add clippy rustfmt.
To ensure your changes will be accepted please check them with:
cargo fmt -- --check
cargo clippy --all-targets -- -D warnings
In addition, ensure all tests are passing with cargo test
It is recommended to run the cargo bench command.
The benchmarks directory contains a library that is dedicated to benchmarking the
Roaring library by using a set of real-world datasets. It is also advised to run the benchmarks
on a bare-metal machine, running them on the base branch and then on the contribution PR
branch to better see the changes.
Those benchmarks are designed on top of the Criterion library, you can read more about it on the user guide.
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you shall be dual licensed as above, without any additional terms or conditions.
Some operations are accelerated with SIMD, implemented with the fearless_simd crate. When the std feature is
enabled, the best available SIMD instruction set is detected at runtime on x86 and x86-64; otherwise, it is determined
by the target features enabled at compile time (e.g. with -C target-cpu=native).