Experiment with a macro system inspired by KL1 language. #2716
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
|
Very strange, all tests pass on my local machine... |
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.
Some time ago I've stumbled on some interesting historical code, and couldn't help myself but implement it for Scryer.
I still don't know how useful it might be, I barely see any really useful use-case, but at least it gives a sense of locality for goal expansion. By locality I mean that only explicitly marked terms are expanded.
More information about macro system in the comments in macros.pl. The easiest way to understand how it works it to check unit tests and compare them to
macros_tests.stdout.What do you think does it make sense?