Compose macro (^# tag) #211
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
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.
Highly experimental and subject to change. Not all of the #154 ideas have been implemented yet. This one corresponds to the Arc/Anarki ssyntax as mentioned in the wiki page. I designed it to be even more powerful, based on some experience with Hissp's spiritual predecessor Drython (and a few other languages). You can almost write straight-up Lissp inside a symbol, with enough escapes (which is mostly useless, but there if you need it). Unlike Arc, it's not built into the Lissp reader, but requires a reader tag. Its expansion is also a lot more complex and kind of opaque compared to Arc's. Some fairly complex functions can be implemented as terse one-liners. Implementation is the best name.
It's definitely one of the more complex macros bundled, but still implemented in about a page of Lissp, and suprisingly a lot of that is in a single boolean expression trying to decide if the thing we just read is callable. It's defined pretty late in the file and really leverages the other bundled macros.