Replace continuation-style internal WPgen blocks#1
Open
yawen-guan wants to merge 1 commit into
Open
Conversation
yawen-guan
changed the title
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
1 participant
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 removes the continuation-style internal WPgen blocks
Wpgen_let_trm_contandWpgen_seq_cont, and reuses the existingWpgen_let_trmandWpgen_seqinstead.This aligns the internal WPgen with the representation used by tactics in
WPTactics.vand lemmas inWPValid.v. The "standard" blocks expose an intermediate postcondition, which gives automation more flexibility: tactics can either split the computation, or recover the old continuation-style reasoning withxlet_trm_cont(as seen inWPTactics.v).Context: I was reasoning about programs written in the untyped imperative lambda calculus with
Wpgen.