From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: order of evaluation
Date: Sun, 23 Jun 2013 15:46:02 +0200 [thread overview]
Message-ID: <87k3llaqjp.fsf@gnu.org> (raw)
In-Reply-To: 87li6959oz.fsf@pobox.com
Andy Wingo <wingo@pobox.com> skribis:
> Not sure what to do. The part of me that wants to do aggressive CSE
> wants to transform to a form that fixes order of evaluation, but the
> part of me that wants to be able to shuffle values using the Dybvig
> algorithm wants to do the direct form. Dunno!
I don’t know either ;-), but I think the guideline should be to give as
much freedom as possible to the compiler.
Leaving the evaluation order unspecified is one way to do it; fixing it
internally it not contradictory with that, as long as it remains
Officially Unspecified.
My €2e-3.
Ludo’.
next prev parent reply other threads:[~2013-06-23 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 10:10 order of evaluation Andy Wingo
2013-06-17 13:49 ` Noah Lavine
2013-06-17 20:14 ` Andy Wingo
2013-06-18 0:39 ` Noah Lavine
2013-06-18 1:06 ` William ML Leslie
2013-06-23 13:46 ` Ludovic Courtès [this message]
2013-07-03 18:57 ` order of evaluation, letrec-values, and define-values Mark H Weaver
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k3llaqjp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
/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.
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).