Add ImmutableRangeMap.toImmutableRangeMap with Key, Value, and Merge Functions (#6822)Issue 6822 #7482
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.
Description
This PR implements a new
Collector
method calledtoImmutableRangeMap
, which allows building anImmutableRangeMap
from a stream of elements. This functionality is useful when dealing with overlapping ranges, where a custommergeFunction
is used to handle overlapping cases.Key Features:
keyFunction
): A function to derive the range key from the input elements.valueFunction
): A function to extract the values from the input elements.mergeFunction
): A binary operator to resolve values when ranges overlap.Code Explanation
The method
toImmutableRangeMap
uses aTreeRangeMap
to collect elements, while handling overlapping ranges:mergeFunction
is applied to merge the values.ImmutableRangeMap
, constructed from the collected ranges and values.Usage Example
Here's an example of how the new method can be used:
Test Coverage
mergeFunction
correctly handles conflicts.ImmutableRangeMap
is accurately constructed with non-overlapping ranges.ImmutableRangeMap
.Related Issues
Fixes #6822.