From: Richard Jones <rich@annexia.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Feature request : Tuples vs. records
Date: Fri, 23 Feb 2007 13:34:50 +0000 [thread overview]
Message-ID: <20070223133450.GA26686@furbychan.cocan.org> (raw)
In-Reply-To: <20070223.103945.99613677.garrigue@math.nagoya-u.ac.jp>
On Fri, Feb 23, 2007 at 10:39:45AM +0900, Jacques Garrigue wrote:
> On the other hand structural typing avoids extra definitions, and
> allows more code sharing and polymorphism. One cannot imagine ML
> without structural tuples. In ocaml, you have also objects that can
> mimic records, and polymorphic variants for sum types.
The penalty of having the extra definitions wouldn't be so bad if
'type t = ...' could appear inside let statements (ie. not just at the
top level). At the moment, type definitions are often a long way away
from where they are used.
Rich.
--
Richard Jones
Red Hat UK Limited
next prev parent reply other threads:[~2007-02-23 13:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 15:34 Frederic GAVA
2007-02-22 16:16 ` David Teller
2007-02-23 1:39 ` Jacques Garrigue
2007-02-23 13:34 ` Richard Jones [this message]
2007-02-23 13:43 ` Till Varoquaux
2007-02-23 14:14 ` Nicolas Pouillard
2007-02-23 1:45 ` Jon Harrop
2007-02-23 16:32 ` Lukasz Stafiniak
2007-02-24 13:43 ` Lukasz Stafiniak
2007-02-24 15:50 ` Brian Hurt
2007-02-24 18:14 ` skaller
-- strict thread matches above, loose matches on Subject: below --
2007-02-22 10:25 David Teller
2007-02-22 10:42 ` [Caml-list] " Andrej Bauer
2007-02-22 12:41 ` skaller
2007-02-22 13:55 ` David Teller
2007-02-22 15:44 ` Jon Harrop
2007-02-22 19:45 ` Tom
2007-02-22 23:26 ` skaller
2007-02-22 15:28 ` Andreas Rossberg
2007-02-22 15:57 ` Till Varoquaux
[not found] ` <45DDC424.2020804@ens-lyon.org>
2007-02-22 16:57 ` Till Varoquaux
2007-02-22 17:19 ` brogoff
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070223133450.GA26686@furbychan.cocan.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).