From: Rob Browning <rlb@defaultvalue.org>
Cc: djurfeldt@nada.kth.se, guile-devel@gnu.org
Subject: Re: About 'futures'
Date: Wed, 09 Mar 2005 13:50:15 -0600 [thread overview]
Message-ID: <87mztclhu0.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <ljk6ogr6b4.fsf@troy.dt.e-technik.uni-dortmund.de> (Marius Vollmer's message of "Wed, 09 Mar 2005 20:02:39 +0100")
Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:
> So futures are clearly faster than threads (as expected). Nice!
Indeed, and as I think someone may have mentioned, we definitely need
some clarification in the docs, since they don't make it clear how
futures differ from threads.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-03-09 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 18:04 About 'futures' Marius Vollmer
2005-03-08 20:52 ` Mikael Djurfeldt
2005-03-08 23:35 ` Kevin Ryde
2005-03-09 15:15 ` Marius Vollmer
2005-03-09 19:02 ` Marius Vollmer
2005-03-09 19:50 ` Rob Browning [this message]
2005-03-08 21:37 ` Rob Browning
2005-03-09 15:17 ` Marius Vollmer
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=87mztclhu0.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=djurfeldt@nada.kth.se \
--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).