From: Daniel Hartwig <mandyke@gmail.com>
To: guile-devel@gnu.org
Subject: Re: Record type printers for SRFI 45 promises and SRFI 41 streams
Date: Mon, 8 Apr 2013 07:13:09 +0800 [thread overview]
Message-ID: <CAN3veRejd6CuGJh32WpMd5gy6fja7-8T2J9+3aNaTA-HtQUFRg@mail.gmail.com> (raw)
In-Reply-To: <20130407164935.GA22923@lotus.destinee.acro.gen.nz>
On 8 April 2013 00:49, Chris K. Jester-Young <cky944@gmail.com> wrote:
> Hi all,
>
> I've attached record type printers for SRFI 45 promises and SRFI 41
> streams. I've tried to make promise-visit more self-documenting with
> the use of keyword arguments; let me know if you think that's an
> improvement!
>
> Also as discussed with Mark H Weaver, I've currently implemented the
> format for promises as #<promise => ...> for unevaluated promises, and
> #<promise = ...> for evaluated ones. Hopefully this is is easy to read
> and will clearly distinguish between the two types, and still look
> different from core promises too.
I dont see much value in distinguishing between eager and lazy,
particularly as this leads to an unusual display format. What
difference does it make how the object was constructed?
Also, this is not avoiding "#<procedure" as suggested? A simple
"#<promise OBJECT-ADDRESS>" is succinct and sufficient.
next prev parent reply other threads:[~2013-04-07 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 16:49 Record type printers for SRFI 45 promises and SRFI 41 streams Chris K. Jester-Young
2013-04-07 17:01 ` Mark H Weaver
2013-04-07 23:13 ` Daniel Hartwig [this message]
2013-04-07 23:19 ` Daniel Hartwig
2013-04-08 19:31 ` Mark H Weaver
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=CAN3veRejd6CuGJh32WpMd5gy6fja7-8T2J9+3aNaTA-HtQUFRg@mail.gmail.com \
--to=mandyke@gmail.com \
--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).