From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: 11198@debbugs.gnu.org, guile-devel <guile-devel@gnu.org>
Subject: Re: bug#11198: prefab structs in guile
Date: Fri, 06 Jul 2012 00:03:09 +0200 [thread overview]
Message-ID: <87ipe13lya.fsf@pobox.com> (raw)
In-Reply-To: <874npldga9.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 05 Jul 2012 23:55:26 +0200")
On Thu 05 Jul 2012 23:55, ludo@gnu.org (Ludovic Courtès) writes:
> So I’d be in the ‘define-serializable-struct’ camp, so to speak.
That's a valid position to have in general. I can also imagine cases in
which you would choose other things. It's a spectrum.
> Prefabs raise an number of interesting issues. For instance, what’s the
> meaning of #s(sprout bean #f 17) in a module where ‘sprout’ is unbound?
Prefab structs are not modular. It is the same as in a module where
`sprout' is bound. Reading #s(sprout bean #f 17) may create an RTD if
needed, but it does not create any bindings.
> types are compared by name.
As the documentation clearly indicates :), prefab structs are indeed
compared by name, though in a combination with other characteristics
(number of fields, and more characteristics for racket).
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-07-05 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.61.1204072212190.6107@commlink.zdv.uni-tuebingen.de>
2012-07-05 8:00 ` prefab structs in guile Andy Wingo
2012-07-05 20:57 ` bug#11198: " Ludovic Courtès
2012-07-05 21:06 ` Andy Wingo
2012-07-05 21:55 ` Ludovic Courtès
2012-07-05 22:03 ` Andy Wingo [this message]
2012-07-05 22:14 ` Ludovic Courtès
2012-07-05 22:06 ` Andy Wingo
[not found] ` <877gui7i3y.fsf__23815.4873405167$1341492684$gmane$org@pobox.com>
2012-07-05 13:42 ` Thien-Thi Nguyen
2012-07-05 15:21 ` Andy Wingo
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=87ipe13lya.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=11198@debbugs.gnu.org \
--cc=guile-devel@gnu.org \
--cc=ludo@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).