From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: [VM] Tail recursion and multiple values
Date: Wed, 04 Mar 2009 00:45:16 +0100 [thread overview]
Message-ID: <87ab825fxv.fsf@gnu.org> (raw)
In-Reply-To: m3hc2bpld1.fsf@pobox.com
Hello,
Andy Wingo <wingo@pobox.com> writes:
> The compiler is almost to the point that it can replace the interpreter,
> semantically. What is needed is to read and compile toplevel definitions
> one at a time, so we can e.g. change the reader, or the other dynamic
> things that people expect. Then if that's the case, then we can just hit
> the user with the one-time cost, for the long-term benefit.
>
> This would also allow us to move closer to having a single codepath,
> which has its benefits, broader tail-recursion among them.
Yes, that's a significant benefit. But I think we can only afford it
once the compiler is sufficiently fast. IMO Guile targets short-lived
programs (aka. "scripts") more than, say, Ikarus, which is why
"compilation" (be it actual compilation or bare memoization) time
matters.
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-03-03 23:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 14:27 [VM] Tail recursion and multiple values Ludovic Courtès
2009-02-28 14:45 ` Ludovic Courtès
2009-03-01 20:31 ` Andy Wingo
2009-03-01 23:48 ` Ludovic Courtès
2009-03-02 18:03 ` Andy Wingo
2009-03-02 21:55 ` Ludovic Courtès
2009-03-02 23:15 ` Andy Wingo
2009-03-02 23:33 ` Andreas Rottmann
2009-03-02 23:43 ` Eduardo Cavazos
2009-03-03 23:45 ` Ludovic Courtès [this message]
2009-03-04 22:11 ` Clinton Ebadi
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=87ab825fxv.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).