DRAFT of simplify-implication RPC endpoint
#239
Draft
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
* remove obsolete substitutor * update haskell.nix nad haskell-backend in the lock
…plify-implication
geo2a
force-pushed
the
georgy/simplify-implication
branch
from
2e5ac7e
to
42c9c44
Compare
geo2a
force-pushed
the
georgy/simplify-implication
branch
from
f69de20
to
56c35eb
Compare
geo2a
force-pushed
the
georgy/simplify-implication
branch
2 times, most recently
from
53de170
to
49c4e83
Compare
geo2a
force-pushed
the
georgy/simplify-implication
branch
from
8af8b5b
to
e3eb94c
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.
Implements runtimeverification/haskell-backend#3787
Needs:
kore-rpc-types(part ofhaskell-backend) that specify the new RPC types: Types specifying thesimplify-implicationRPC endpoint haskell-backend#3614This PR is a bare-bones implementation of the new
simplify-implicationRPC endpoint. We currently only returnImplicationValidif the antecedent matches consequent and the constrains are empty. If matching is failing we returnImplicationInvalid. Otherwise,ImplicationUnknown.Note that the diff is so big because the PR a new Kore definition
simplify-implication.korefor integration tests.