-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LISP forms don't properly rewrite variables #5
Comments
eliaslfox
added a commit
that referenced
this issue
Aug 31, 2021
Previously lisp nodes were rewritten with a code walker to allow them to access renamed variables. This seemed to fragile so lisp nodes now must declare which local variables they wish to use. The lisp node's form will then be wrapped in a let block during codegen which will unrename the requested variables. Fixes #5
eliaslfox
added a commit
that referenced
this issue
Aug 31, 2021
Previously lisp nodes were rewritten with a code walker to allow them to access renamed variables. This seemed to fragile so lisp nodes now must declare which local variables they wish to use. The lisp node's form will then be wrapped in a let block during codegen which will unrename the requested variables. Fixes #5
eliaslfox
added a commit
that referenced
this issue
Aug 31, 2021
Previously lisp nodes were rewritten with a code walker to allow them to access renamed variables. This seemed to fragile so lisp nodes now must declare which local variables they wish to use. The lisp node's form will then be wrapped in a let block during codegen which will unrename the requested variables. Fixes #5
eliaslfox
added a commit
that referenced
this issue
Aug 31, 2021
Previously lisp nodes were rewritten with a code walker to allow them to access renamed variables. This seemed to fragile so lisp nodes now must declare which local variables they wish to use. The lisp node's form will then be wrapped in a let block during codegen which will unrename the requested variables. Fixes #5
eliaslfox
added a commit
that referenced
this issue
Aug 31, 2021
Previously lisp nodes were rewritten with a code walker to allow them to access renamed variables. This seemed to fragile so lisp nodes now must declare which local variables they wish to use. The lisp node's form will then be wrapped in a let block during codegen which will unrename the requested variables. Fixes #5
eliaslfox
added a commit
that referenced
this issue
Aug 31, 2021
Previously lisp nodes were rewritten with a code walker to allow them to access renamed variables. This seemed to fragile so lisp nodes now must declare which local variables they wish to use. The lisp node's form will then be wrapped in a let block during codegen which will unrename the requested variables. Fixes #5
macrologist
added a commit
to macrologist/coalton
that referenced
this issue
Oct 10, 2023
# This is the 1st commit message: Labels for all loop varieties more parser tests # This is the commit message coalton-lang#2: doh # This is the commit message coalton-lang#3: Fix: bad codgen for bare loop # This is the commit message coalton-lang#4: Fix: bad parse of while-let node after label feature # This is the commit message coalton-lang#5: Add: loop documentation to intro doc # This is the commit message coalton-lang#6: requested malarchy # This is the commit message coalton-lang#7: more tests; no break/continue from lambdas
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: