From: Alex <agrambot@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 27177@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#27177: 26.0.50: Macroexpanding cl-loop and friends (make-symbol usage)
Date: Wed, 31 May 2017 20:02:30 -0600 [thread overview]
Message-ID: <87lgpc79e1.fsf@gmail.com> (raw)
In-Reply-To: <87poeoy0zk.fsf@drachen> (Michael Heerdegen's message of "Thu, 01 Jun 2017 03:01:51 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> With print-circle and print-gensym bound, I think the result does not
> really read worse than how it would look like with with `cl-gensym'
> generated code.
That's much better, though I still think it could/should be better. For
example, if you have multiple uninterned symbols with different
symbol-names, they're all referenced by #number, and use the same
counter.
It also seems to make the output uglier as well. Consider:
(macroexpand '(cl-loop for x in '(1 2 3)
for y in '(a b c)
repeat 10
repeat 20
collect (list x y)))
Note the expressions using #5#. I suppose the 0 is being shared.
It would also be nice if instead of many --cl-var-- variables,
particular clauses would result in different symbol-names. For instance,
if the `repeat' clause made a symbol called --cl-repeat--. This would
further help readability.
Also, using gensym could help 3rd-party packages. I usually use
macrostep to expand macros and the value of print-circle has no effect
on its expansions. macrostep individually prints out each uninterned
symbol using prin1; can this approach be easily modified to get the same
result as macroexpand?
PS: The first line of the documentation of print-circle only mentions
that it affects recursive structures. Perhaps it should mention the
"shared substructures" part in the first line for emphasis?
next prev parent reply other threads:[~2017-06-01 2:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 23:23 bug#27177: 26.0.50: Macroexpanding cl-loop and friends (make-symbol usage) Alex
2017-05-31 23:51 ` Michael Heerdegen
2017-06-01 0:29 ` Alex
2017-06-01 0:52 ` npostavs
2017-06-01 1:01 ` Michael Heerdegen
2017-06-01 2:02 ` Alex [this message]
2017-06-02 3:27 ` Michael Heerdegen
2017-06-02 4:42 ` Alex
2017-06-02 23:09 ` Michael Heerdegen
2017-06-02 23:17 ` npostavs
2017-06-02 23:46 ` Alex
2017-06-03 2:33 ` Stefan Monnier
2017-06-04 0:24 ` Alex
2017-06-06 4:20 ` Stefan Monnier
2017-06-06 20:31 ` Alex
2020-08-24 14:53 ` Lars Ingebrigtsen
2017-06-01 0:29 ` npostavs
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=87lgpc79e1.fsf@gmail.com \
--to=agrambot@gmail.com \
--cc=27177@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=npostavs@users.sourceforge.net \
/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.