SilFrontend API for Viper frontend usage#732
Merged
Merged
Conversation
…m/viperproject/silver into meilers_term_plugin_deactive_flag
This was referenced Aug 17, 2023
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.
SilFrontendby actual Viper frontends. Compared to working withVerifierinstances directly, these take care of plugins (i.e., they run the relevant plugin phases automatically; command line arguments can be used to select which plugins to run) and don't require calling a bunch of boilerplate methods. Compared to existingSilFrontendclasses, these are made to be used by frontends (without parsing etc.) and correctly pass command line options to plugins.Tested with adapted versions of Prusti and Nagini.