From: Andreas Rossberg <rossberg@ps.uni-sb.de>
To: skaller <skaller@users.sourceforge.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Operator overloading
Date: Fri, 09 Mar 2007 17:28:31 +0100 [thread overview]
Message-ID: <45F18B2F.20307@ps.uni-sb.de> (raw)
In-Reply-To: <1173452871.22738.91.camel@rosella.wigram>
skaller wrote:
>
> I'm sorry to write so poorly. This isn't the comparison I'm
> drawing.
>
> Consider *implementing* typeclasses with records,
> as in Oleg's Ocaml examples.
>
> Ok, now replace the records with classes. Classes
> are more powerful because they provide
>
> (a) state
> (b) inheritance etc
Records and classes are not in the same category. Records and *objects*
are. OTOH, objects *are* basically records, except that they usually
come with more expressive typing, particularly allowing recursive types
and subtyping. State is still orthogonal - records can have state, too.
Classes are a mechanism for *creating* objects (and in weaker languages
than OCaml, for defining subtyping relations). Take away inheritance and
you are basically left with fancy syntax for a function creating a
record of mutually recursive closures over some local variables.
> They also don't make the weak assumption of an
> abstraction (possibly with default methods as in Haskell)
> and a single instantiation: in C++ at least you can
> have sequence of more derived classes.
Please distinguish subtyping and inheritance. Type classes can express
something akin to nominal interface subtyping, e.g.
class C a where m1 :: t1
class C a => D a where m2 :: t2
But it's true that they do only provide a very weak form of inheritance
(via default methods).
> So the type model associated with this implementation
> can do more than the one just using plain records:
> records aren't typeclasses, so the class based implementation
> can't be compared with them:
>
> records classes
> typeclasses ???????
I cannot make much sense of this diagram, because of the category
mismatch I mentioned above.
> Anyhow my ARGUMENT was actually that using classes
> subsumes plain old records .. and classes are
> limited by the covariance problem, so records
> must be limited too.
Something like the covariance problem does not occur with type classes
(or modules, for that matter) because they decouple types from
interfaces. A type class is merely an interface, witnessed by a record,
the actual type is abstracted out. With OO, this is mingled together (an
object type *is* its interface), which produces that nasty recursion
where all the type problems originate.
So the difference is in the way these features factorise abstraction,
rather than in the intrinsic expressiveness of the underlying
primitives. Operationally, you can view dictionaries as detached
"vtables". This detachment allows them to be used in more flexible ways,
and avoid nuisances like the binary method issue.
Of course, it also makes inheritance a rather alien concept.
--
Andreas Rossberg, rossberg@ps.uni-sb.de
next prev parent reply other threads:[~2007-03-09 16:28 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 7:36 oleg
2007-03-09 11:09 ` [Caml-list] " skaller
2007-03-09 13:52 ` Andreas Rossberg
2007-03-09 15:07 ` skaller
2007-03-09 16:28 ` Andreas Rossberg [this message]
2007-03-10 3:13 ` skaller
-- strict thread matches above, loose matches on Subject: below --
2007-03-09 16:40 Robert Fischer
2007-03-09 17:25 ` Jon Harrop
2007-03-08 23:20 Robert Fischer
2007-03-09 10:31 ` Jon Harrop
2007-03-08 20:02 Robert Fischer
2007-03-08 20:15 ` Michael Hicks
2007-03-08 20:50 ` Brian Hurt
2007-03-08 21:05 ` Tom
2007-03-08 21:31 ` Brian Hurt
2007-03-08 22:09 ` Michael Vanier
2007-03-08 22:34 ` Till Varoquaux
2007-03-09 16:02 ` Brian Hurt
2007-03-10 3:23 ` skaller
2007-03-08 22:14 ` Ian Zimmerman
2007-03-09 10:29 ` Jon Harrop
2007-03-09 16:28 ` Ian Zimmerman
2007-03-08 23:51 ` skaller
2007-03-09 7:23 ` Tom
2007-03-09 9:24 ` skaller
2007-03-09 9:32 ` Tom
2007-03-09 10:00 ` skaller
2007-03-09 10:14 ` Jon Harrop
2007-03-09 10:38 ` Jon Harrop
2007-03-09 10:20 ` Jon Harrop
2007-03-09 12:08 ` Andrej Bauer
2007-03-09 12:48 ` Jacques Carette
2007-03-09 13:24 ` Andreas Rossberg
2007-03-10 5:08 ` Daniel Andor
2007-03-10 5:33 ` David Thomas
2007-03-08 14:41 [Caml-list] F# Robert Fischer
2007-03-08 17:30 ` Roland Zumkeller
2007-03-08 17:54 ` Brian Hurt
2007-03-08 19:40 ` [Caml-list] Operator overloading Jon Harrop
2007-03-08 20:44 ` Brian Hurt
2007-03-08 22:24 ` Fernando Alegre
2002-04-15 17:05 [Caml-list] operator overloading Issac Trotts
2002-04-14 4:15 Issac Trotts
2002-04-13 8:43 forsyth
2002-04-13 5:26 Issac Trotts
2002-04-13 1:32 Gurr, David (MED, self)
2002-04-12 19:08 Issac Trotts
2002-04-13 8:48 ` William Chesters
2002-04-13 13:58 ` Brian Rogoff
2002-04-13 15:31 ` William Chesters
2002-04-14 3:10 ` Brian Rogoff
2002-04-13 9:00 ` Daniel de Rauglaudre
2002-04-13 21:35 ` Johan Georg Granström
2002-04-14 1:50 ` Jacques Garrigue
2002-04-15 16:22 ` Jun P.FURUSE
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=45F18B2F.20307@ps.uni-sb.de \
--to=rossberg@ps.uni-sb.de \
--cc=caml-list@inria.fr \
--cc=skaller@users.sourceforge.net \
/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).