Change And/Or-type structures #521
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
mtshiba
force-pushed
the
perf_or_type
branch
from
c9cbf69 to
df837d7
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.
In this PR,
Type::{And, Or}, which previously had a structure of(Box<Type>, Box<Type>), will be flattened to(Set<Type>)(however,Andhas a structure of(Vec<Type>)due to non-commutativity, which will be described later).This ensures the commutativity of
Orand fixes related bugs. This fix also improves performance, especially for largeAnd/Ortypes. AlthoughAndtypes are semantically commutative, it usesVecbecause it is necessary to fix the order of trials when used as overloaded types.