From: Andy Wingo <wingo@pobox.com>
To: Chaos Eternal <chaoseternal@shlug.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: discussion: serialize procedures and continuations
Date: Sun, 23 Mar 2014 21:25:03 +0100 [thread overview]
Message-ID: <87siq8slwg.fsf@pobox.com> (raw)
In-Reply-To: <CAGyY8NufzfsuY3oqPT4ECzrE0wqAss=qthjvE1+CW2__FjuqAA@mail.gmail.com> (Chaos Eternal's message of "Thu, 15 Aug 2013 21:47:52 +0800")
On Thu 15 Aug 2013 15:47, Chaos Eternal <chaoseternal@shlug.org> writes:
> Hence, it is reasonable to expect a way to serialize the closures to
> disks and/or remote machines over network.
Agreed. Guile 2.2's compiler might be able to do this, with some
modification -- take a closure and tree-shake out its dependencies,
packaged into an ELF image. Similar to save-lisp-and-die in some ways.
But that's a bit expensive to do; there should probably be a way of
doing it at compile-time instead of at run-time.
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2014-03-23 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 13:47 discussion: serialize procedures and continuations Chaos Eternal
2013-08-17 12:55 ` Ludovic Courtès
2014-03-23 20:25 ` Andy Wingo [this message]
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=87siq8slwg.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=chaoseternal@shlug.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).