From: Kevin Ryde <user42@zip.com.au>
Subject: promises mutex
Date: Mon, 06 Sep 2004 11:39:17 +1000 [thread overview]
Message-ID: <87hdqcqipm.fsf@zip.com.au> (raw)
Is there a theory on having a mutex for each promise?
I see it has the effect of preventing two threads simultaneously
forcing, but I wonder if it'd be easier to allow that, just a single
mutex to protect the final store of the result.
This would be smaller and faster, and might even be beneficial for
some crazy cross-thread recursive forcing. It'd be in keeping with
leaving most syncing up to the application (ie. allowing most anything
not actively harmful).
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2004-09-06 1:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87hdqcqipm.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).