Syntax for backend types#638
Merged
Merged
Conversation
This was referenced Dec 21, 2022
Contributor
Author
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
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 syntax for domain types and domain functions that have interpretations given by the backend.
This functionality used to be available in the AST only.
Syntax example (as discussed in a previous Viper meeting):
Consistency checks ensure that the given input program has interpretations for the current backend.
This domain type and function can be used like any other type and function, but will be interpreted to be the respective SMTLIB/Boogie type by Silicon and Carbon, respectively.
Frontends using the existing BackendFunction AST nodes will have to be adapted slightly (in particular, the declarations of those functions now have to be added to the program using domains, which was not the case before), but there are some constructors and deconstructors to keep existing code working where possible.
Accompanying PRs will modify Silicon and Carbon accordingly.