fix rangeMapFindIn containment filter#885
Open
cuiweixie wants to merge 1 commit intokoka-lang:devfrom
Open
Conversation
Entries should lie fully inside the query range; require both bounds instead of either.
Member
|
Thanks for the PR. Can you give an example where I can see the difference? Is this onHover inside vs code? |
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
2 participants
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.
Summary
In
rangeMapFindIn, the filter used||, so a range satisfied the predicate if either edge was inside the query span, which matches far too many entries. Use&&so only ranges fully contained in the query range are kept (consistent with needing bothrangeStart >= startandrangeEnd <= end).