all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Andrea Corallo <acorallo@gnu.org>
Cc: 71120@debbugs.gnu.org, "Mattias Engdegård" <mattiase@acm.org>,
	"Philip Kaludercic" <philipk@posteo.net>,
	"Philippe Schnoebelen" <phs@lmf.cnrs.fr>
Subject: bug#71120: 29.3; buglet in cl-loop
Date: Wed, 29 May 2024 21:45:26 -0400	[thread overview]
Message-ID: <jwvr0dkyt4q.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <yp1fru0s3pe.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Wed, 29 May 2024 17:33:49 -0400")

>>   (let* ((<fresh-variable> 1) (--cl-var-- nil))
>>     (while (<= <fresh-variable> 100)
>>       (let ((_i <fresh-variable>))
>> 	(setq --cl-var-- (cons (random 6) --cl-var--))
>> 	(setq <fresh-variable> (+ <fresh-variable> 1))))
>>     (nreverse --cl-var--))
>>
>> I have added Mattias and Stefan to the CCs, as they'll probably have
>> more qualified comments to add.

Not really: There's a similar problem with `cl-destructuring-bind` and
similarly, when I started to look at the corresponding code I quickly
gave up.

At least for `cl-destructuring-bind` I think I understand the intended
behavior well enough that I might be able to implement code which
behaves as we want (tho I don't know how to *modify* the existing code
to reach that stage).

In the case of `cl-loop` the intended behavior is much too complex for
my poor head, so I don't think I'd be able to decide whether it does the
right thing for all cases.


        Stefan






  parent reply	other threads:[~2024-05-30  1:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22  8:43 bug#71120: 29.3; buglet in cl-loop Philippe Schnoebelen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-29 20:47 ` Philip Kaludercic
2024-05-29 21:33   ` Andrea Corallo
2024-05-29 21:49     ` Andrea Corallo
2024-05-30  1:45     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-05-30  9:25   ` Mattias Engdegård
2024-05-30 13:14     ` Andrea Corallo
2024-05-30 14:51       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-30 15:41         ` Andrea Corallo
2024-05-30 15:45           ` Mattias Engdegård
2024-05-30 17:15             ` Andrea Corallo
2024-05-30 17:18               ` Mattias Engdegård
2024-05-30 17:42                 ` Andrea Corallo
2024-05-31  4:30                   ` Gerd Möllmann
2024-05-31  8:29                   ` Mattias Engdegård
2024-06-03 15:24                     ` Andrea Corallo
2024-06-03 15:32                       ` Mattias Engdegård
2024-06-03 15:42                         ` Andrea Corallo
2024-06-03 16:24                           ` Mattias Engdegård

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=jwvr0dkyt4q.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=71120@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=mattiase@acm.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    --cc=phs@lmf.cnrs.fr \
    /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.