Add a IntervalUnion.shift operation
#58
Merged
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.
Moving an interval can overflow in case the new values of the interval can't be represented by the type.
In the majority of use cases this can probably be ignored, but in those cases where an overflow does occur, an assumption was made that the most likely desirable behavior is to move the interval as far as possible. I.e., 'clamp' the operation to the possible value range.
But, to ensure the caller can still tell overflowed operations apart from fully successful shift operations, the actual amount by which the interval is shifted is included in the return value.
In addition: while writing unit tests for
shift, I noticed some errors onEmptyIntervalUnionoperations, which are now fixed.Some things left to consider:
TSize? Found a workaround/no longer a requirement.unsafeShiftinfinite loops on "infinity" values.