From: akater <nuclearspace@gmail.com>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: emacs-devel@gnu.org
Subject: Re: defmacro with built-in gensym declaration and initialization
Date: Thu, 21 Jan 2021 19:34:02 +0000 [thread overview]
Message-ID: <875z3q6q51.fsf@gmail.com> (raw)
In-Reply-To: <87o8hj9vl9.fsf@tcd.ie>
[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]
"Basil L. Contovounesios" <contovob@tcd.ie> writes:
> Let's just say I would sooner see native arglists gain support for
> keyword arguments ;).
>
> For non-native arglists, we could always extend cl-defmacro or some
> other definition definer.
Sorry, I suspect I misunderstood. What's a native arglist? Doesn't
defmacro already have native support for &optional and &rest keywords?
> I was referring to the arity of the macro being defined, not that of
> defmacro.
I guess I'm confused, again. The arity of macro being defined remains
exactly the same. See the --partition-by example in the original
message. defmacro/&gensym is a drop-in replacement; it doesn't change
any arities.
> It and its variant macroexp-let2* are relevant wherever the macro author
> wants to avoid evaluating an argument more than once, but improvements
> are always welcome.
That's usually called “once-only” but unlike once-only, macroexp-let2
also requires a test function which is exactly why I called it “an
overcomplicated once-only”. &gensym is also relevant wherever the macro
author wants to avoid evaluating an argument more than once, and where
the argument needs to be evaluated unconditionally, but it's more
concise, both in terms of token count and nesting depth. One variation
of defmacro/&gensym accessible in the linked repository does perform the
same elimination of bindings as macroexp-let2, only it uses a hardcoded
test function, namely macroexp-const-p.
>> Since we're moving to
>> natively compiled Elisp, I was thinking it's going to become less
>> relevant in near future, and &gensym covers most use cases of once-only.
>
> I don't see how native compilation changes how existing and new Elisp
> macros ought to be written.
What's the purpose of TEST in macroexp-let2, then, other than to
minimise bindings in the expansion? (Which I presume is only relevant
when Elisp's byte compiler is used to compile the expanded form.)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2021-01-21 19:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 8:15 defmacro with built-in gensym declaration and initialization akater
2021-01-20 13:46 ` Basil L. Contovounesios
2021-01-20 15:09 ` Stefan Monnier
2021-01-20 16:47 ` Robin Tarsiger
2021-01-20 19:28 ` akater
2021-01-20 20:55 ` Basil L. Contovounesios
2021-01-21 19:34 ` akater [this message]
2021-01-21 20:50 ` Stefan Monnier
2021-01-21 20:50 ` Basil L. Contovounesios
2021-01-21 21:05 ` Stefan Monnier
2021-01-21 21:23 ` Basil L. Contovounesios
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875z3q6q51.fsf@gmail.com \
--to=nuclearspace@gmail.com \
--cc=contovob@tcd.ie \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.