Refactor VerificationService #724
Merged
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 refactoring prepares
VerificationService
to be asynchronous (in a future PR that makesVerificationService::verify
return aFuture
, upgrading toreqwest >= 0.10
).The Prusti server has been designed to handle concurrent verification requests, but so far we used it sequentially because there were concurrency issues (now fixed) in Viper.
@vakaras I changed the service to take a single program, not a vector. It makes it easier to limit the number of concurrent verification requests.
The diff is negative 🎉