From: Lars Ingebrigtsen <larsi@gnus.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 57907@debbugs.gnu.org
Subject: bug#57907: 29.0.50; Using keywords with cl-loop
Date: Sun, 18 Sep 2022 14:20:20 +0200 [thread overview]
Message-ID: <87wna027sr.fsf@gnus.org> (raw)
In-Reply-To: <87tu54dh3t.fsf@posteo.net> (Philip Kaludercic's message of "Sun, 18 Sep 2022 12:03:50 +0000")
Philip Kaludercic <philipk@posteo.net> writes:
> It seems to me that it would be nice to support these too, as keywords
> have the superficial advantage of being a bit more readable due to their
> additional highlighting, and for some people it makes the macro a bit
> more comfortable to use since it doesn't have to feel like you are using
> a whole new language, but instead these are just keyword arguments to an
> unusual function call.
I think it'd just lead to even more confusion, since they aren't really
keyword arguments. Because then you'd have to say
(loop ...
:do (progn (foo) (bar)))
But you can say
(loop ...
do (foo)
(bar))
next prev parent reply other threads:[~2022-09-18 12:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 12:03 bug#57907: 29.0.50; Using keywords with cl-loop Philip Kaludercic
2022-09-18 12:20 ` Lars Ingebrigtsen [this message]
2022-09-18 12:28 ` Philip Kaludercic
2022-09-18 12:37 ` Lars Ingebrigtsen
2022-09-18 12:46 ` Philip Kaludercic
2022-09-19 8:06 ` Lars Ingebrigtsen
2022-09-19 10:16 ` Philip Kaludercic
2022-09-19 12:52 ` Lars Ingebrigtsen
[not found] ` <handler.57907.B.166350264228653.ack@debbugs.gnu.org>
2022-09-18 12:26 ` bug#57907: Acknowledgement (29.0.50; Using keywords with cl-loop) Philip Kaludercic
2022-09-18 20:12 ` Philip Kaludercic
2022-09-18 12:38 ` bug#57907: 29.0.50; Using keywords with cl-loop Gerd Möllmann
2022-09-18 12:52 ` Philip Kaludercic
2022-09-18 13:01 ` Gerd Möllmann
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=87wna027sr.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=57907@debbugs.gnu.org \
--cc=philipk@posteo.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 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).