[Heapster] Don't use Coq let-bindings in Heapster specs #1545
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 PR adds a function
sawLet
to thesaw-core
Prelude which is used in Heapster instead ofsaw-core
's usual sharing mechanism to ensure certain shared variables are not translated to Coq let-bindings. This is because Coq very much likes to unfold let-bindings, which is bad for examples in which unfolding let-bindings results in exponential explosion (see theexp_explosion
example added in this PR). By having an explicit function (sawLet
), we can control when we unfold in the proof automation.This PR also cleans up the SHA512 example.