Unify spars and spars_merge documentation - #88
Merged
Merged
Conversation
README and DESIGN now describe both candidate generators as available on every inverted index type with every comparator, differing only in traversal. Align generator and sequence-comparator class comments with that wording.
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
1 participant
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
sparsandspars_mergeboth apply to every inverted index type and every comparator, and differ only in key-major versus row-major traversal.spars_mergeto specific comparators orinverted_term.FilteredSearch,MergeSearch, andBaseSequenceComparatorcomments with the same scope.Test plan
bazel test //:test_main(optional sanity)