From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Delimited continuations to the rescue of futures
Date: Thu, 22 Nov 2012 00:28:54 +0100 [thread overview]
Message-ID: <87txsicz7t.fsf@gnu.org> (raw)
In-Reply-To: 87y5hzritn.fsf@gnu.org
ludo@gnu.org (Ludovic Courtès) skribis:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> I guess the one remaining concern I have is that if there are any
>> long-running futures in the process, then any 'touch' could take a very
>> long time to complete, even if the future it is waiting for is a very
>> short job.
>>
>> For example, (par-map - '(1 2 3)) could take several minutes to complete
>> if (par-map process-image list-of-images) is being done in another
>> thread.
>
> Right. That’s actually easy to fix, but the advantage of the current
> solution is that it uses less code. Anyway, you’re probably right, so
> I’ll do that.
I didn’t do that (as discussed in this thread), and ended up merging
wip-nested-futures as is.
Thanks,
Ludo’.
next prev parent reply other threads:[~2012-11-21 23:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 23:36 Delimited continuations to the rescue of futures Ludovic Courtès
2012-11-17 4:38 ` Mark H Weaver
2012-11-17 13:43 ` Ludovic Courtès
2012-11-17 16:56 ` Mark H Weaver
2012-11-17 22:00 ` Ludovic Courtès
2012-11-18 22:19 ` Mark H Weaver
2012-11-20 19:20 ` Ludovic Courtès
2012-11-21 12:18 ` Peter TB Brett
2012-11-21 13:36 ` Ludovic Courtès
2012-11-21 16:45 ` Peter TB Brett
2012-11-21 21:19 ` Ludovic Courtès
2012-11-21 23:28 ` Ludovic Courtès [this message]
2013-01-14 2:34 ` Nala Ginrut
2013-01-14 10:37 ` 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=87txsicz7t.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).