Draft
Conversation
This reverts commit 1041119.
Collaborator
Author
|
20 minutes later i found an application :-| I am somewhat worried about performance implications -- need to rebase and test it out |
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
1 participant
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.
In the encoding state, we can keep track of an array of literals that get prepended onto every added clause. This feature could potentially allow for more code re-use because any encoding program can be conditioned by some set of variables.
The semantic interpretation of an encoding program slightly changes to "if all the assumed vars are false then ..."
However, right now I have no application for it and it unnecessarily complicates the encoding monad proofs. This draft PR is in case I ever find such an application and want to revive the implementation.