From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: guile-devel@gnu.org
Subject: Re: About 'futures'
Date: Wed, 09 Mar 2005 16:15:19 +0100 [thread overview]
Message-ID: <lju0nkrgu0.fsf@troy.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <66e540fe05030812526a7ccb6f@mail.gmail.com> (Mikael Djurfeldt's message of "Tue, 8 Mar 2005 21:52:35 +0100")
Mikael Djurfeldt <mdjurfeldt@gmail.com> writes:
>> Would that make sense?
>
> I don't think so for obvious reasons. It would not make sense to
> spawn new pthreads for the kind of usage patterns for which futures
> are intended. In my opinion it's better to scrap futures entirely than
> to provide the suggested implementation above.
Ok, I see. (I have no intention to remove futures.)
I think we need to be more concrete about the pool of threads that
futures use. It should be documented and there should be a way to
control the number of threads, for example.
(I will also try to benchmark them, but there is a bug right now that
prevents me from using a huge number of threads... (that bug is not
related to futures))
> Note also that futures, by their nature, necessarily needs to be
> maintained together with the guile-core rather than being provided
> by a separate package.
Why is that so?
_______________________________________________
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 15:15 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 [this message]
2005-03-09 19:02 ` Marius Vollmer
2005-03-09 19:50 ` Rob Browning
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=lju0nkrgu0.fsf@troy.dt.e-technik.uni-dortmund.de \
--to=marius.vollmer@uni-dortmund.de \
--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).