all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 29866@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
Subject: bug#29866: 27.0.50; cl-loop: Calculate the array length just once
Date: Thu, 28 Dec 2017 06:36:55 +0900 (JST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1712280620320.16455@calancha-pc> (raw)
In-Reply-To: <jwvwp17evv9.fsf-monnier+emacsbugs@gnu.org>



On Wed, 27 Dec 2017, Stefan Monnier wrote:

>> X-Debbugs-CC: monnier@iro.umontreal.ca
>
> Thanks.
>
>> It looks sensible to calculate the array length just once,
>> instead of recalculate it on each iteration:
>
> I tend to agree, but I don't know very much about the intended semantics
> of Common Lisp's `loop` macro, nor about cl-loop's implementation (tho
> I admit I did mess with it without being really sure what I was doing).
While studying this code I found easier to hack if we use gensym's
instead of make-symbol; otherwise, the code creates several symbols with
the same printed representation "--cl-var--".  For example, with 
current code you can read expansions with something like:

(let* ((--cl-var-- 'foo)
        (--cl-var-- 'bar))

I prefer to read:

(let* ((--cl-var--1 'foo)
        (--cl-var--2 'bar))

Do you have any preference in these cases?





  reply	other threads:[~2017-12-27 21:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-27 16:10 bug#29866: 27.0.50; cl-loop: Calculate the array length just once Tino Calancha
2017-12-27 20:13 ` Tino Calancha
2017-12-27 20:20   ` Lars Ingebrigtsen
2017-12-27 20:54 ` Stefan Monnier
2017-12-27 21:36   ` Tino Calancha [this message]
2017-12-28  1:27     ` Drew Adams
2017-12-28  1:49       ` Noam Postavsky
2017-12-28  1:52         ` Drew Adams
2017-12-28  2:39     ` Stefan Monnier
2017-12-28 17:21       ` Tino Calancha
2018-01-07 15:39   ` Tino Calancha
2020-05-06  2:21 ` Noam Postavsky

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=alpine.DEB.2.20.1712280620320.16455@calancha-pc \
    --to=tino.calancha@gmail.com \
    --cc=29866@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.