[move-prover] Refactored options creation for better reuse #250_173#480
Open
[move-prover] Refactored options creation for better reuse #250_173#480
Conversation
Contributor
|
/canary |
|
☀️ Canary successful |
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
4 participants
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.
Motivation
This PR enhances #439 by making it easier to specify prover options for applications outside of core Move. Without this refactoring, the options have to be passed as strings or the entire
run_move_proverfunction needs to be copied to customize them. The refactoring enables "outside" prover users to reuserun_move_proverby replicating/augmenting code in a much shorterexecutefunction only.