Skip to content

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

@cespare

Description

@cespare

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.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions