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

Handle non-semantic nodes preceding the bound form of quote, unquote, etc #2

Open
cespare opened this issue Nov 28, 2014 · 0 comments

Comments

@cespare
Copy link
Owner

cespare commented Nov 28, 2014

For example

@ ; surprisingly,
; this is a valid deref.
x

This happens with derefs, quotes, unquotes, unquote splices, syntax quotes, metadata, and the 'ignore next form' dispatch macro.

Right now the intermediate non-semantic nodes (comments, newlines) interfere if we're using ignoreNonSemantic: false.

This isn't something a human would probably write but we need to handle it anyway.

Open question: where should the non-semantic nodes be bound? (Maybe just put them after the form.)

@cespare cespare changed the title [parser] Handle non-semantic nodes preceding the bound form of quote, unquote, etc Handle non-semantic nodes preceding the bound form of quote, unquote, etc Nov 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant