unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Tino Calancha <tino.calancha@gmail.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 29866@debbugs.gnu.org
Subject: bug#29866: 27.0.50; cl-loop: Calculate the array length just once
Date: Wed, 27 Dec 2017 17:27:05 -0800 (PST)	[thread overview]
Message-ID: <eb971105-2e0f-426d-a7cb-994c6aa2f1b4@default> (raw)
In-Reply-To: <alpine.DEB.2.20.1712280620320.16455@calancha-pc>

> 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))

That's the same variable, `--cl-var--', bound
first to `foo' and then to `bar'.

> I prefer to read:
> 
> (let* ((--cl-var--1 'foo)
>        (--cl-var--2 'bar))

That's two different variables.

> Do you have any preference in these cases?

As presented here, they are not equivalent.
Check the actual code to see if the second
can, in fact, be used in place of the first.





  reply	other threads:[~2017-12-28  1:27 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
2017-12-28  1:27     ` Drew Adams [this message]
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

  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=eb971105-2e0f-426d-a7cb-994c6aa2f1b4@default \
    --to=drew.adams@oracle.com \
    --cc=29866@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=tino.calancha@gmail.com \
    /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).