Remove some uses of 'unliteral' #125
Merged
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
added 3 commits
March 17, 2015 08:17
As a result, symbolicMerge now behaves uniformly for all type instances of 'SBV a'.
As a result, they now behave uniformly for all type instances of 'SBV a'.
LeventErkok
added a commit
that referenced
this pull request
Mar 17, 2015
Remove some uses of 'unliteral'
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.
These uses of
unliteral :: SBV a -> aand equality on typeawere causing errors in our SAW tools, due to our non-standard usage of theSymWordclass.The revised definitions are also a step towards implementing #124.