Revising the syntax of vprops in Pulse #132
Merged
Conversation
This file contains 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
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.
The syntax of vprops in Pulse now coincides with their syntax in F*.
The main enabler was the addition of overloaded quantifier tokens in F*, i.e., FStarLang/FStar#3149
Now, you can write
for vprops in both F* and Pulse contexts.
The Pulse parser no longer has special treatment for vprops. So, this also gets rid of the `@ syntax of embedding F* terms inside Pulse vprop, since the syntax of a Pulse vprop is now just the syntax of F* terms.
This fixes a couple of open issues: #50 #14 (and gets rid of some WHY WHY WHY remarks in Tahina's Pulse code).