From: Philip Kaludercic <philipk@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57907@debbugs.gnu.org
Subject: bug#57907: 29.0.50; Using keywords with cl-loop
Date: Sun, 18 Sep 2022 12:28:18 +0000 [thread overview]
Message-ID: <87leqgdfz1.fsf@posteo.net> (raw)
In-Reply-To: <87wna027sr.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 18 Sep 2022 14:20:20 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> 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))
Why would this be necessary? I am not saying that `cl-loop' should be
converted into a proper keyword-macro, just that each `:foo' in a
loop-keyword position ought to be interpreted as `foo'.
next prev parent reply other threads:[~2022-09-18 12:28 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
2022-09-18 12:28 ` Philip Kaludercic [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87leqgdfz1.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=57907@debbugs.gnu.org \
--cc=larsi@gnus.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.