We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Wow! The reader emits fake calls to unquote functions— allowing for custom syntax-quote-like macros if you don’t like the one built into the reader:
'~foo
(clojure.core/unquote foo)
'~@foo
(clojure.core/unquote-splicing foo)
Someone in 2008 wanted a syntax-quote without symbol resolution (i.e. quasi-quote) here, and Rich added the fake calls to allow it:
It looks like a canonical quasiquote was published four years later in 2012 (which I had starred and forgot about): https://github.com/brandonbloom/backtick
source: searched on clojurians slack for “syntax quote resolve” and saw all this unearthed by @NoahTheDuke here: https://clojurians.slack.com/archives/C03S1KBA2/p1656779374489749
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Wow! The reader emits fake calls to unquote functions— allowing for custom syntax-quote-like macros if you don’t like the one built into the reader:
'~foo
=>(clojure.core/unquote foo)
'~@foo
=>(clojure.core/unquote-splicing foo)
Someone in 2008 wanted a syntax-quote without symbol resolution (i.e. quasi-quote) here, and Rich added the fake calls to allow it:
It looks like a canonical quasiquote was published four years later in 2012 (which I had starred and forgot about):
https://github.com/brandonbloom/backtick
source: searched on clojurians slack for “syntax quote resolve” and saw all this unearthed by @NoahTheDuke here:
https://clojurians.slack.com/archives/C03S1KBA2/p1656779374489749
The text was updated successfully, but these errors were encountered: