Conversation
Pulls in fix for RoaringBitmap/RoaringBitmap#61
Member
|
👍 |
Contributor
|
👍 after travis |
Contributor
Author
|
Contributor
Author
|
The big question is: Do we want this added to an 0.8.3-rc4 ? |
Contributor
|
@drcrallen I think it is fine for this to wait. |
xvrl
added a commit
that referenced
this pull request
Jan 7, 2016
Update bytebuffer-collections to 0.2.4
Member
|
@fjy in that case we should mark roaring as unsafe to use in 0.8.x? |
Contributor
|
I think 0.8.3-rc4 is appropriate, as roaring is not an experimental feature so bug fixes are important. |
Contributor
|
0.8.4 would be cool too. |
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.
Fixes #2218
Pulls in fix for RoaringBitmap/RoaringBitmap#61