Zach/ast changes #36
Closed
Zach/ast changes #36
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
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.
In working with first-order specs I've found it useful to have a Predicate node of the form "p/n" indicating a predicate p of arity n. Similarly for ASP, while working with completion results it is useful to have a symmetric Predicate node. The way Atoms (in both ASTs) are currently parsed and formatted, we omit the "/n" (arity information). I think this is the right choice, although technically writing "p(t1,t2)" is syntax sugar for "p/2(t1,t2)" which I think provides a theoretical justification for having Predicate behind the scenes.