From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.7-291-g4a1cdc9
Date: Sun, 07 Apr 2013 00:49:15 +0200 [thread overview]
Message-ID: <87bo9r1dhw.fsf@gnu.org> (raw)
In-Reply-To: 871uapwk02.fsf@tines.lan
Mark H Weaver <mhw@netris.org> skribis:
> I'd like to hear opinions on how to print promises. Here are mine:
>
> * I don't like #<eager ...> and #<lazy #<procedure ...>>.
>
> * Both forms should start with #<promise ...>, because from a user's
> point of view that is the type.
+1
> * We should avoid printing "#<procedure" in there. Some kind of
> location tag would be useful, but let's make it more compact.
Yeah, (number->string (object-address x) 16) should be enough.
Ludo’.
prev parent reply other threads:[~2013-04-06 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1UNwJ4-0003EO-Dd@vcs.savannah.gnu.org>
2013-04-05 6:48 ` [Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.7-291-g4a1cdc9 Mark H Weaver
2013-04-05 12:36 ` Chris K. Jester-Young
2013-04-05 13:19 ` Chris K. Jester-Young
2013-04-06 22:49 ` Ludovic Courtès [this message]
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=87bo9r1dhw.fsf@gnu.org \
--to=ludo@gnu.org \
--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).