Minor: Split equivalence code into smaller modules #8235
Closed
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.
Which issue does this PR close?
Part of #8064
Rationale for this change
As equivalence and ordering become ever more important, I would like to break the code up into smaller modules to make it harder to handle.
At almost 3000 lines with several large classes that are overlapping. the existing
equivalence.rs
is hard to understand.I would like to break it up into smaller modules.
In fact I didn't even realize there were so many equivalence tracking structures until I started looking at the code more closely.
What changes are included in this PR?
Move
EquivalenceClass
,EquivalenceGroup
,OrderingEquivalenceClass
,ProjectionMapping
,EquivalenceProperties;
and into their own modules, and then update some internal apis to keep the interfaces clearAre these changes tested?
Are there any user-facing changes?
Existing tests