From: Andy Wingo <wingo@pobox.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Compiler Branch
Date: Fri, 20 Jan 2012 21:49:57 +0100 [thread overview]
Message-ID: <87y5t2rte2.fsf@pobox.com> (raw)
In-Reply-To: <CA+U71=OLUU+w8eOMaJdWByBWa9U3wtLKvOO0ngWAySJ-3bjQrg@mail.gmail.com> (Noah Lavine's message of "Sun, 8 Jan 2012 16:15:47 -0500")
Heya Noah,
A brief note:
On Sun 08 Jan 2012 22:15, Noah Lavine <noah.b.lavine@gmail.com> writes:
> I do think there's a problem with plain CPS, though - it forces you to
> pick an order for the evaluation of function arguments. I would like
> to use CPS with some sort of parallel-call operator, so we can leave
> the order undefined (maybe at some point an optimizer will want to
> adjust the order). What do you think?
>
> I also noticed that at the end of that blog post you said you were
> considering ANF versus CPS for Guile (I assume you'd already decided
> that you didn't like Tree-IL). Does this mean you decided on CPS?
I guess I'd like to see if it's a good idea or not. We definitely do
need a parallel binding operator. I haven't already decided on it but I
am interested.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-01-20 20:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 4:39 Compiler Branch Noah Lavine
2011-12-13 8:47 ` Andy Wingo
2011-12-13 13:52 ` Noah Lavine
2012-01-07 1:00 ` Andy Wingo
2012-01-08 0:42 ` Noah Lavine
2012-01-08 14:53 ` Andy Wingo
2012-01-08 21:15 ` Noah Lavine
2012-01-20 20:49 ` Andy Wingo [this message]
2011-12-18 20:42 ` Ludovic Courtès
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=87y5t2rte2.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=noah.b.lavine@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.
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).