feat: parse range constraints from binfile #375
Merged
Conversation
This file contains 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
This puts in place code for detecting range constraints.
This puts through an initial (and rather rough) implementation of range constraints. Its a big confusing at this stage, since we currently have a notion of "TypeConstraint" and "RangeConstraint".
This simply refactors the existing TypeConstraint to use a bound rather than a type. This is a precursor to replacing the existing RangeConstraint with this.
This completely eliminates the old RangeConstraint and replaces it with the modified TypeConstraint.
DavePearce
force-pushed
the
373-parse-range-constraints-from-binfile
branch
from
8790c14
to
fd72633
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This adds support for user-defined range constraints. Specifically, such range constraints can be over expressions rather than just columns.