Improve @expressions
performance by pre processing sets
#815
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.
Description
This PR replaces #773 the improvement is the better performance in constructing JuMP
@expression
s.This new PR only contains the set pre-processing from #773, so it is easier to review.
These set operations are performed more frequently than necessary. Pre-processing the sets before building expressions is more efficient as it requires strictly less work and allocations.
What type of PR is this? (check all applicable)
Related Tickets & Documents
Replaces #773
Checklist
How this can be tested
This should not alter any outputs.
Post-approval checklist for GenX core developers
After the PR is approved