POC: Use IndexSet rather than Vec for OrderingEquivalenceClass
#14136
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
alamb
force-pushed
the
alamb/exponential_planning_2
branch
from
544e058 to
832975c
Compare
alamb
force-pushed
the
alamb/exponential_planning_2
branch
from
832975c to
d5f3819
Compare
github-actions
bot
added
core
|
This doesn't seem to be super promising for now, so closing it |
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.
WIP as I am still in the process of
resolve_overlapWhich issue does this PR close?
UNIONandORDER BYqueries #13748Rationale for this change
I am trying to make many of the overlap algorthms constant time rather than polynomial in the number of expressions
What changes are included in this PR?
Use IndexSet rather than
Vecfor OrderingEquivalenceClassAre these changes tested?
by existing CI
Are there any user-facing changes?