Repository navigation
Add more CRoaring users to the README - #951
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The README lists only a handful of systems that use CRoaring. A search of GitHub found several more widely used projects that build against it:
roaring/3.0.0, includesroaring/roaring.hhroaring/roaring.handroaring/roaring64.hindeps/oblib/src/lib/roaringbitmapFindCroaring.cmake,be/src/util/roaring-bitmap.hthird_party/roaring_bitmaproaringsrc/storage/common/croaring.cppmcmake/croaring.cmakeIt also notes that NVIDIA's cuDF and cuCollections query serialized Roaring bitmaps on the GPU. They implement the Roaring format with their own CUDA code; CRoaring is used only in cuDF's tests and benchmarks.
The PR also removes a stray double space before the Redis link.