From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Matt Armstrong <matt@rfc20.org>
Cc: emacs-devel@gnu.org
Subject: Re: Addressing confusion over uninterned symbols
Date: Wed, 14 Apr 2021 19:16:35 -0400 [thread overview]
Message-ID: <jwvh7k8v4un.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87sg3sa2kk.fsf@rfc20.org> (Matt Armstrong's message of "Wed, 14 Apr 2021 16:06:35 -0700")
> Are there reasons that macros like macroexp-let2* avoid using gensym?
The reason is/was to avoid cons'ing the corresponding strings (I
recommend `print-gensym` and `print-circle` for the rare cases where
you need to look at the macroexpanded code).
Maybe we should have a variant of `print-gensym` which prints the
symbol's address along with the rest?
Stefan
prev parent reply other threads:[~2021-04-14 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 22:20 Addressing confusion over uninterned symbols Matt Armstrong
2021-04-14 23:06 ` Matt Armstrong
2021-04-14 23:16 ` Stefan Monnier [this message]
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvh7k8v4un.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=matt@rfc20.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).