From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: What are the arguments in favor of delay/force in eval.c?
Date: Thu, 15 Dec 2005 08:10:49 +1100 [thread overview]
Message-ID: <871x0f75ba.fsf@zip.com.au> (raw)
In-Reply-To: <87oe3pwpeu.fsf@trouble.defaultvalue.org> (Rob Browning's message of "Fri, 09 Dec 2005 20:23:53 -0800")
Rob Browning <rlb@defaultvalue.org> writes:
>
> You may have already noticed this, but I think the semantics of
> SRFI-45 force/delay are supposed to be a strict superset of R5RS
> force/delay, so in theory we might be able to have just one type of
> promise.
As far as I can tell there's two types of promises, one generated by
`delay' the other by `lazy', so if you only use delay+force you get
r5rs, if you use lazy+force you get the new style.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-12-14 21:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 21:14 What are the arguments in favor of delay/force in eval.c? Rob Browning
2005-12-07 21:31 ` Kevin Ryde
2005-12-07 22:47 ` Rob Browning
2005-12-08 0:29 ` Kevin Ryde
2005-12-08 0:52 ` Rob Browning
2005-12-10 0:11 ` Kevin Ryde
2005-12-10 4:23 ` Rob Browning
2005-12-14 21:10 ` Kevin Ryde [this message]
2005-12-08 0:57 ` Ken Raeburn
2005-12-08 1:28 ` 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=871x0f75ba.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).