From: Brian Hurt <bhurt@janestcapital.com>
To: Michael Hicks <mwh@cs.umd.edu>
Cc: Robert Fischer <RFischer@RoomAndBoard.com>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Operator overloading
Date: Thu, 08 Mar 2007 15:50:58 -0500 [thread overview]
Message-ID: <45F07732.3020707@janestcapital.com> (raw)
In-Reply-To: <200703082015.l28KFrfh003479@loompa.cs.umd.edu>
Michael Hicks wrote:
>This discussion reminds of a paper that appeared at POPL 2007 about the
>relationship between ML modules and Haskell type classes. The former are
>really good for organizing your namespace and making dependencies and
>operations explicit. The latter are really good at (disciplined) operator
>overloading (which is convenient as many here have argued). The paper looks
>at how the two can be combined (essentially, operator overloading is
>implicit functor instantiation), so you can have the best of both worlds.
>
>
The reason type classes were implemented in Haskell was as a sane way to
implement a generic equality operator. Myself, I question the need for
a generic equality operator.
Brian
next prev parent reply other threads:[~2007-03-08 20:51 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 20:02 Robert Fischer
2007-03-08 20:15 ` Michael Hicks
2007-03-08 20:50 ` Brian Hurt [this message]
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
-- 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-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
2007-03-10 3:13 ` skaller
2007-03-08 23:20 Robert Fischer
2007-03-09 10:31 ` Jon Harrop
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=45F07732.3020707@janestcapital.com \
--to=bhurt@janestcapital.com \
--cc=RFischer@RoomAndBoard.com \
--cc=caml-list@yquem.inria.fr \
--cc=mwh@cs.umd.edu \
/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).