From: <tomas@tuxteam.de>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: syntax taste: use of unquote in macros
Date: Tue, 31 Mar 2020 11:19:38 +0200 [thread overview]
Message-ID: <20200331091938.GC5995@tuxteam.de> (raw)
In-Reply-To: <2fc3bffd-da8d-eb4b-094b-649cf76e3fee@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
On Mon, Mar 30, 2020 at 04:43:47PM -0700, Matt Wette wrote:
[...]
> The other thing about match that is attractive is that use of
> quasiquote+unquote is "reflexive" (or maybe self-adjoint?)
> in the following sense:
>
> '(foo "bar") => (match-lambda (`(foo ,val) `(foo ,val))) => '(foo "bar")
Sorry, my head just exploded :-)
Will take it more slowly later today. Thanks for the riddle.
Cheers
-- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2020-03-31 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 15:11 syntax taste: use of unquote in macros Matt Wette
2020-03-29 22:07 ` Zelphir Kaltstahl
2020-03-30 10:34 ` tomas
2020-03-30 23:43 ` Matt Wette
2020-03-31 9:19 ` tomas [this message]
2020-03-30 13:07 ` Arne Babenhauserheide
2020-03-31 16:56 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200331091938.GC5995@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).