Expand simple let #30
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.
Add expansion for
letsyntax to the expander. To make this work I started to add the macro expansion facility.It uses the VM to expand the supplied syntax and thus forms the skeleton for user-defined syntax.
However it currently doesn't take care of hygiene (not required so far) and is probably not supporting all cases yet.
It adds an expander for a simple let, which expands into the corresponding lambda expressions.
At a later point I'll think about whether it's preferable to compile let expressions differently, which would required to preserve them and parse them into an expression.
Important
This doesn't implement named let as that requires a proper implementation of letrec first