From: William Lovas <wlovas@stwing.upenn.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Understanding why Ocaml doesn't support operator overloading.
Date: Sun, 1 Dec 2002 18:41:55 -0500 [thread overview]
Message-ID: <20021201234154.GA4301@force.stwing.upenn.edu> (raw)
In-Reply-To: <200212011730.SAA10480@pauillac.inria.fr>
On Sun, Dec 01, 2002 at 06:30:55PM +0100, Pierre Weis wrote:
> > As an exercise, try to write a useful function that operates
> > on just 'a's -- you'll find it a challenge :) (in fact, i think there's a
> > theorem in one of Philip Wadler's papers that says the *only* function of
> > type 'a -> 'a in a purely functional language is the identity function).
>
> This is a theorem that was stated about $\lambda$-calculus long time
> ago, way before Phil Wadler's papers, back to Reynolds as I remember.
That's probably true -- i just happened to remember it from a Wadler paper.
> The challenge you proposed is not so difficult in Caml. You can easily
> define functions that operates on justs'a's, or even just return plain
> 'a's!
>
> Objective Caml version 3.06+18 (2002-11-07)
>
> # raise;;
> - : exn -> 'a = <fun>
> # ignore;;
> - : 'a -> unit = <fun>
Mmm, this certainly is a useful use of polymorphism without parametrized,
types, but the challenge i was trying to propose was more to the spirit of
the original 'a -> 'a theorem: by "useful function that operates on just
'a's", what i meant was essentially "a non-trivial function of type
'a -> 'a", which is (i hope) a significantly more difficult challenge :)
Polymorphism as used in `raise' and `ignore' strikes me as more language
magic than anything else -- although useful in practice, i have a strong
intuition that from a certain theoretical perspective, namely that of
purely functional languages, they're not so interesting. So, to clarify,
while they are practical uses of polymorphism, they're not what i had in
mind when i wrote the above paragraph.
Thanks for the corrections and pointers!
cheers,
William
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-12-01 23:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 21:02 Jørgen Hermanrud Fjeld
2002-11-28 21:27 ` Jørgen Hermanrud Fjeld
2002-11-29 15:26 ` Xavier Leroy
2002-11-29 15:42 ` Christophe Raffalli
2002-11-29 16:52 ` Nicolas Cannasse
2002-11-29 17:26 ` Michal Moskal
2002-11-30 0:00 ` Mike Lin
2002-11-30 10:24 ` Michal Moskal
2002-11-30 23:06 ` Mike Lin
2002-11-30 21:41 ` William Lovas
2002-12-01 17:30 ` Pierre Weis
2002-12-01 23:41 ` William Lovas [this message]
2002-12-02 9:52 ` Remi VANICAT
2002-11-30 21:47 ` Pierre Weis
2002-12-01 7:40 ` Christophe Raffalli
2002-11-30 21:36 ` Pierre Weis
2002-11-30 21:33 ` Pierre Weis
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=20021201234154.GA4301@force.stwing.upenn.edu \
--to=wlovas@stwing.upenn.edu \
--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