Repository navigation
Conversation
Discrete types (Long, Date, DateTime, Time) now return closed bounds from the effective start/end, as Integer already did. Decimal and Quantity use the intervals' own bounds so open bounds stay open. Adds open-bound test cases.
…ntersect A null open bound is unknown, so the result keeps that bound null and open while the known bounds still decide overlap (TestIntersectNull* now pass and are no longer excluded). Quantity unit checks now use every non-null bound, so a null closed bound no longer reports a unit mismatch.
vfrank66
force-pushed
the
issue_144-add-interval-in-intersect
branch
from
October 11, 2026 17:12
39e7dbd to
024065a
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.