From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: Switching to a SRFI-45 compliant force/delay.
Date: Mon, 11 Sep 2006 10:51:06 +1000 [thread overview]
Message-ID: <87zmd71b0l.fsf@zip.com.au> (raw)
In-Reply-To: <87ejujpanr.fsf@raven.defaultvalue.org> (Rob Browning's message of "Sun, 10 Sep 2006 16:24:56 -0700")
Rob Browning <rlb@defaultvalue.org> writes:
>
> The implementation works (it passes all of the tests they provide),
> and I believe could completely replace Guile's existing eval.c
> force/delay, but I wanted to know if anyone knew of a reason it
> shouldn't.
I remember I thought it could go in C in the core nicely enough, or at
least just extending `force' in the core and leaving the actual
`eager' to the srfi module perhaps. I don't remember the details
though, except it might be nice to lose the mutexes at the same time
:), for speed and size.
http://lists.gnu.org/archive/html/guile-devel/2005-12/msg00050.html
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-09-11 0:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 23:24 Switching to a SRFI-45 compliant force/delay Rob Browning
2006-09-11 0:51 ` Kevin Ryde [this message]
2006-09-11 1:33 ` Rob Browning
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=87zmd71b0l.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).