caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Andrej Bauer <Andrej.Bauer@andrej.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Type Inference and Overloading
Date: Mon, 10 Apr 2006 15:42:48 +0200	[thread overview]
Message-ID: <200604101542.48960.Andrej.Bauer@andrej.com> (raw)
In-Reply-To: <c1490a380604100151s256d05y13cc8ffa11580770@mail.gmail.com>

On Monday 10 April 2006 10:51, Tom Primožič wrote:
> I would like to pose one really perverse question (perverse because it
> mentions overloading).

To add insult to perversion, I will mention Haskell. Have you had a look at 
Haskell's type classes? They allow you to write "+" or "print" to mean many 
different things, while not doing actual overloading.

So if all you care about is usability for programmer, and not so much about 
overloading for the sake of overloading, type classes might be a nice option.

Andrej


  parent reply	other threads:[~2006-04-10 13:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10  8:51 Tom Primožič
2006-04-10 11:57 ` [Caml-list] " skaller
2006-04-10 13:42 ` Andrej Bauer [this message]
2006-04-10 14:06 ` Brian Hurt
2006-04-10 14:43   ` Tom Primožič
2006-04-11 16:11 ` Stefan Monnier

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=200604101542.48960.Andrej.Bauer@andrej.com \
    --to=andrej.bauer@andrej.com \
    --cc=caml-list@yquem.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).