Decision vars & global exprs in where strings #490
Merged
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.
Fixes issue(s) #450
Summary of changes in this pull request:
Since there is a strict order of things in the backend (parameters -> variables -> expressions -> constraints -> objective), we will have already constructed variables by the time we construct expressions and will have access to both variables and expressions by the time we reach constraints. Therefore, their existence can be checked in the constraint/objective where string. It makes some things less verbose.
Reviewer checklist: