Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

intersect seem not working correctly #13

Closed
v4vale opened this issue Aug 31, 2015 · 1 comment
Closed

intersect seem not working correctly #13

v4vale opened this issue Aug 31, 2015 · 1 comment

Comments

@v4vale
Copy link

v4vale commented Aug 31, 2015

According to README and according to logic, 123[2-7] & 123[4-5] should returns 123[4-5] instead it returns 123[4-7].
@dimitri
Copy link
Owner

dimitri commented Aug 31, 2015

Thanks! I'm quite surprised to see such a bug gone undetected for so long, thanks for finding and reporting it...

dimitri added a commit that referenced this issue Sep 1, 2015
@dimitri
Fix prefix_range intersection again, fix #13.
1d18e33 
We need to be careful about empty first/last values and special case them.
df7cb added a commit that referenced this issue Jan 9, 2016
@df7cb
Update expected/queries.out with the prefix_range fix. (#13)
27b4b43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dimitri @v4vale