change translation of if-statement to not rely on optimizer for readable output #478
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.
Previously, the translated condition in the if-statement translation was computed by the Scala expression
allStateAssms ==> transalteExpInWand(cond)
. In the standard case,allStateAssms
is set to true and Carbon's Boogie optimizer gets rid of the implication's left hand side.Now, the translated condition is computed such that if
allStateAssms
is true, then the left hand side is removed direcly without requiring the optimizer. This produces more readable output when doing experiments where the optimizer is switched off.