From: "Linus Björnstam" <linus.internet@fastmail.se>
To: "Mark H Weaver" <mhw@netris.org>
Cc: guile-user@gnu.org
Subject: Re: Srfi-159/166 - monadic formatting for guile
Date: Sun, 16 Jun 2019 22:30:06 +0200 [thread overview]
Message-ID: <1ede9515-bbd0-4233-8bfa-2f3d02d74a19@www.fastmail.com> (raw)
In-Reply-To: <87wohm2g1k.fsf@netris.org>
Well, in the written-shared/pretty-shared case, Alex Shinn (I just ported his reference implementation) relies on display/write for everything except lists and vectors, and those are, from what I can tell, exhaustively checked for cycles.
trimmed/lazy I have to have a read through in some other way than black-on-white text on my 3.5" phone.
Best regards
Linus
--
Linus Björnstam
On Sun, 16 Jun 2019, at 08:37, Mark H Weaver wrote:
> Hi Linus,
>
> Linus Björnstam <linus.internet@fastmail.se> writes:
>
> > I am not sure I understand what you mean, but i suspect it is already
> > solved, since for simple cases show will use display/write. So unless
> > you try to do advanced formatting of circular lists it will do
> > whatever display or write does. The same thing goes for custom
> > printers.
>
> How do you implement 'written-shared', 'pretty-shared', and
> 'trimmed/lazy'? In particular, how do you avoid non-termination when
> asked to print cyclic data, when the cycle includes a non-standard data
> type printed using a custom printer? For example, what if you print a
> list that includes an object whose custom printer will print output that
> includes the same list that you started with?
>
> Regards,
> Mark
>
prev parent reply other threads:[~2019-06-16 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 13:38 Srfi-159/166 - monadic formatting for guile Linus Björnstam
2019-06-02 20:31 ` Arne Babenhauserheide
2019-06-02 20:41 ` Ludovic Courtès
2019-06-03 5:34 ` Linus Björnstam
2019-06-03 13:07 ` Ludovic Courtès
2019-06-11 22:01 ` Mark H Weaver
2019-06-14 9:38 ` Linus Björnstam
2019-06-16 6:35 ` Mark H Weaver
2019-06-16 16:20 ` John Cowan
2019-06-16 19:30 ` Mark H Weaver
2019-06-18 10:39 ` Linus Björnstam
2019-06-16 20:30 ` Linus Björnstam [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=1ede9515-bbd0-4233-8bfa-2f3d02d74a19@www.fastmail.com \
--to=linus.internet@fastmail.se \
--cc=guile-user@gnu.org \
--cc=mhw@netris.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).