Support externally declared relation names#3
Merged
Conversation
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.
Adds support for declaring some relation names as
#:extern, which allows them to be used unhygenically. This is added to allow starting with a set of known facts which come from Racket (i.e. the source of some other data) for increased dynamicism.These
externsymbols still interact with syntax-spec for scoping, but (likeimported symbols) do not have arity checking. It would be possible to check that they are internally consistent with each other, but that would not get any safety benefit (since the fact set you start solving with could still have the wrong arities). This might be nice to fix but is not needed for a first pass (time is of the essence currently).