From: Christopher Kauffman <kauffman@cs.umn.edu>
To: OCaml <caml-list@yquem.inria.fr>
Subject: Question on polymorphic typing for curried functions
Date: Fri, 24 Aug 2007 14:43:26 -0500 [thread overview]
Message-ID: <46CF34DE.301@cs.umn.edu> (raw)
I am looking for a bit of information on the behavior of curried functions wrt
polymorphic arguments. For instance, in the following example, using a curried
function seems to lose the nice polymorphism that I desire.
# let genf f a b = f a b;;
val genf : ('a -> 'b -> 'c) -> 'a -> 'b -> 'c = <fun>
# let specf = genf (<);;
val specf : '_a -> '_a -> bool = <fun>
# specf 1 2;;
- : bool = true
# specf;;
- : int -> int -> bool = <fun>
An alternative definition for the specific 'specf' maintains polymorphism of its
arguments.
# let specf a b = genf (<) a b;;
val specf : 'a -> 'a -> bool = <fun>
# specf 1 2;;
- : bool = true
# specf 1.0 2.0;;
- : bool = true
# specf;;
- : 'a -> 'a -> bool = <fun>
Is there a set of rules or guidelines that determine when argument types are
specialized versus staying polymorphic?
Cheers,
Chris
next reply other threads:[~2007-08-24 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 19:43 Christopher Kauffman [this message]
2007-08-24 20:25 ` [Caml-list] " Jon Harrop
2007-08-24 21:04 ` Julien Moutinho
2007-08-24 23:32 ` Harrison, John R
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=46CF34DE.301@cs.umn.edu \
--to=kauffman@cs.umn.edu \
--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