Draft of verification API to get discussion started on #2084 #2229
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
cpitclaudel
force-pushed
the
cpitclaudel_API
branch
from
f4b002e to
e285dd0
Compare
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.
To deliver on #2084 we need to determine which functionality to expose as part of a Dafny library API.
I'm hoping that this PR can start the discussion on this. It shows what a minimal API might look like (it's essentially a refactoring of the existing DafnyServer to move the non-REPL parts to a separate library), supporting only (incremental) verification.
@mschlaipfer, in #2084 you mentioned only verifying a program; is that all you need from the API, or do you need more advanced features?