From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, help-gnu-emacs@gnu.org
Subject: RE: Always using let*
Date: Sun, 14 Sep 2014 16:06:17 -0700 (PDT) [thread overview]
Message-ID: <df255af0-c3a3-4bc8-bd37-0abbd0674bbd@default> (raw)
In-Reply-To: <jwvy4tlddv8.fsf-monnier+gnu.emacs.help@gnu.org>
> > (The other reason is that for some Lisps the bindings of `let'
> > can be done in parallel, which can be quicker.)
^^^ ^^^
>
> Urban legend!
Perhaps you would prefer "could" to "can"?
Lisps such as Common Lisp were specifically designed with this
parallel evaluation in mind. The spec (and CLTL(2)) specifically
emphasizes the inherent parallelism (independence) here that
implies the *possibility* of parallel evaluation.
Whether a given Common Lisp implementation takes advantage of
this inherent parallelism is optional. Likewise for the other
explicitly parallel constructs in CL.
For `psetf', for example, CLTL says that "the assignments of
new values are done in parallel. More precisely, all subforms
that are to be evaluated are evaluated from left to right;
after all evaluations have been performed, all of the
assignments are performed in an unpredictable order."
next prev parent reply other threads:[~2014-09-14 23:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 19:46 Always using let* Cecil Westerhof
2014-09-14 21:25 ` Drew Adams
2014-09-15 16:15 ` Drew Adams
[not found] ` <mailman.8924.1410797740.1147.help-gnu-emacs@gnu.org>
2014-09-15 18:01 ` Cecil Westerhof
2014-09-15 22:20 ` Emanuel Berg
2014-09-16 12:05 ` Cecil Westerhof
2014-09-16 22:40 ` Emanuel Berg
2014-09-18 17:02 ` Cecil Westerhof
2014-09-18 21:05 ` Emanuel Berg
2014-09-16 14:23 ` sokobania.01
2014-09-16 16:41 ` Drew Adams
2014-09-16 20:49 ` Stefan Monnier
2014-09-16 22:45 ` Emanuel Berg
[not found] ` <mailman.8998.1410901776.1147.help-gnu-emacs@gnu.org>
2014-09-16 22:48 ` Emanuel Berg
2014-09-17 1:09 ` Stefan Monnier
2014-09-17 1:18 ` Emanuel Berg
2014-09-14 21:40 ` Joe Fineman
[not found] ` <mailman.8868.1410729956.1147.help-gnu-emacs@gnu.org>
2014-09-14 21:41 ` Emanuel Berg
2014-09-14 22:11 ` Cecil Westerhof
2014-09-14 22:56 ` Drew Adams
2014-09-14 22:41 ` Stefan Monnier
2014-09-14 23:06 ` Drew Adams [this message]
[not found] ` <mailman.8871.1410736002.1147.help-gnu-emacs@gnu.org>
2014-09-15 0:47 ` Emanuel Berg
2014-09-15 2:12 ` Pascal J. Bourguignon
2014-09-15 2:22 ` Stefan Monnier
2014-09-15 2:59 ` Pascal J. Bourguignon
2014-09-15 12:31 ` Stefan Monnier
2014-09-15 16:15 ` Drew Adams
2014-09-15 19:05 ` Stefan Monnier
[not found] ` <mailman.8930.1410808006.1147.help-gnu-emacs@gnu.org>
2014-09-15 22:28 ` Emanuel Berg
2014-09-16 0:38 ` Pascal J. Bourguignon
2014-09-15 13:14 ` Barry Margolin
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=df255af0-c3a3-4bc8-bd37-0abbd0674bbd@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@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.