unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mattias Engdegård" <mattias.engdegard@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 71120@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
	Philippe Schnoebelen <phs@lmf.cnrs.fr>
Subject: bug#71120: 29.3; buglet in cl-loop
Date: Thu, 30 May 2024 11:25:46 +0200	[thread overview]
Message-ID: <4ED83CF1-C697-46DF-99D2-56432A1E3B44@gmail.com> (raw)
In-Reply-To: <87cyp4wdj7.fsf@posteo.net>

Philippe Schnoebelen <phs@lmf.cnrs.fr> writes:

> When I need a list of 100 random dice throws I write
> 
> 	(cl-loop for i from 1 to 100 collect (random 6))
> 
> It compiles just fine.
> 
> If instead I use
> 
> 	(cl-loop for _i from 1 to 100 collect (random 6))
> 
> then I get a compilation warning:
> 
> 	foo.el:1:18: Warning: variable ‘_i’ not left unused

Quite unfair that you have no a priori way of knowing whether your variable name is actually the one that `cl-loop` uses for iteration or just one bound for each iteration (as in `dotimes`).

A sloppy reading of Common Lisp's `loop` spec, which we don't need to follow since this isn't CL but we'd be fools to deviate too far from without a good reason, didn't tell me anything.

In particular nothing about whether the user is allowed to alter the variable in order to change the iteration. For example, what should

  (cl-loop for i from 1 to 100
           when (= i 3) do (setq i 98)
           collect i)

return? Perhaps better not touch that.

Thus I don't think there's anything we really need to do here, do you?






  parent reply	other threads:[~2024-05-30  9:25 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
2024-05-30  9:25   ` Mattias Engdegård [this message]
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

  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=4ED83CF1-C697-46DF-99D2-56432A1E3B44@gmail.com \
    --to=mattias.engdegard@gmail.com \
    --cc=71120@debbugs.gnu.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 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).