unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57907-done@debbugs.gnu.org
Subject: bug#57907: 29.0.50; Using keywords with cl-loop
Date: Mon, 19 Sep 2022 10:16:47 +0000	[thread overview]
Message-ID: <874jx3fz3k.fsf@posteo.net> (raw)
In-Reply-To: <87pmfryeiz.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 19 Sep 2022 10:06:12 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>
>> I phrased that clumsily -- while it is a new language, it doesn't always
>> have to feel like one.
>
> And I'm saying that that feeling is a misleading feeling -- we're
> leading the users down the garden path.
>
>> E.g. the repeat-collect example I gave before.
>> If you *can* use keywords, you *can* make some cl-loop invocations
>> appear to be a macro or a function call with keyword-arguments.
>>
>> But of course this wouldn't be the case, as the macro should stay
>> backwards compatible.
>
> I understand that.  But it means that the stated rationale for this
> change does the users a disservice.
>
> So I'm against extending cl-loop in this way.  Gerd has explained why
> it works this way in Common Lisp (because CL doesn't have any other
> choice because that's the way the language works), but we should not
> shoehorn in this accident into Emacs, too.

While it might have had been an accident initially, I don't think it has
to be considered such.  As I said, there are reasons like syntax
highlighting for preferring keyword-symbols.  But if you don't think
this is a good idea, I'll go ahead and close the issue.





  reply	other threads:[~2022-09-19 10:16 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
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 [this message]
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=874jx3fz3k.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=57907-done@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 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).