Experimental Support for Grouping Constraints over Common Patterns - #44
Open
pulsipher wants to merge 20 commits into
Open
Experimental Support for Grouping Constraints over Common Patterns#44pulsipher wants to merge 20 commits into
pulsipher wants to merge 20 commits into
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #44 +/- ##
===========================================
- Coverage 85.82% 69.30% -16.53%
===========================================
Files 6 7 +1
Lines 748 997 +249
===========================================
+ Hits 642 691 +49
- Misses 106 306 +200 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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 experimental support of detecting common constraint patterns, grouping them together, and adding each group as a single
ExaModels.Constraint. Givenmodel::InfiniteModel, the user syntax is simply:or
Initially support is limited to:
If this performs well, we should be able to relax these restriction(s).
Early testers can try this out via:
Possible improvements include: