Skip to content
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

Add a test for unquotes _not_ being first-class syntax #576

Open
masak opened this issue Jan 30, 2023 · 0 comments
Open

Add a test for unquotes _not_ being first-class syntax #576

masak opened this issue Jan 30, 2023 · 0 comments

Comments

@masak
Copy link
Owner

masak commented Jan 30, 2023

In one of the really long-running issues I realize with the force of a pan-galactic gargleblaster that unquotes are holes, not "first-class Qnodes".

In another issue somewhere talking about traversal, I wonder out loud how this will affect traversing quasis, now that they "contain" holes which are not really "there". As I recall it, I provide the question but no satisfactory answer.

Meanwhile, in Bel, I'm asking to add this test in order to properly test a (fairly horrible) behavior that stems from unquotes in Bel being first-class AST objects, and "unhygienic" ones at that, not in any way connected to the surrounding quasiquote in which they were used. (And that is why Bawden insists quote interpolation should be part of the reader, to avoid such a disconnect/spooky action at a distance.)

I'm still not claiming to have any ready answers. (As usual, this is brain-melty.) But I think focusing on Bawden's stance (and the example in masak/bel#427) might help clarify what Alma can do and (maybe) should do in this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant