Repository navigation
Conversation
Replace the per-type except implementations with one evalExceptInterval that compares the closed start/end of both operands: - intervals touching at a boundary now return the remaining part ([0,10] except [10,20] is [0,9]) instead of null - Date/DateTime/Time compare at the values' own precision, not DAY; uncertain comparisons return null - results keep the left operand's original bound and inclusivity on the side that is not cut, so open bounds are no longer shifted - Quantities with comparable units are converted; incomparable units return null instead of an evaluation error Add test cases for each of these.
vfrank66
force-pushed
the
issue_142-add-interval-support-in-except
branch
from
October 11, 2026 17:12
5cd9cd4 to
454ea38
Compare
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.
No description provided.