From: Andreas Rossberg <rossberg@ps.uni-sb.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] strange effect of type annotation
Date: Wed, 11 Aug 2004 14:17:55 +0200 [thread overview]
Message-ID: <411A0E73.4060708@ps.uni-sb.de> (raw)
In-Reply-To: <16665.61343.130286.600455@gargle.gargle.HOWL>
fis@wiwi.hu-berlin.de wrote:
>
>> let good : (int * float) = let x = fst in (x (0,1), x (0., 1.));;
>> let bad : (int * float) = let x: ('a * 'a) -> 'a = fst in (x (0,1), x (0., 1.));;
>
> The type checker sais:
>
>> let bad : (int * float) = let x: ('a * 'a) -> 'a = fst in (x (0,1), x (0., 1.));;
>> ^^^^^^^^
>>This expression has type float * float but is here used with type int * int
This is due to OCaml's counter-intuitive interpretetion of type
variables in type annotations. The 'a is not polymorphic! Rather, it is
considered a monomorphic placeholder for some concrete type (IOW it is
not quantified). The effect is similar to saying
let x: (_ * _) -> _ = fst in (x (0,1), x (0., 1.))
except that you put the additional constraint that all occurances of the
wildcard have to denote the same type.
When the type checker sees the first application of x it then knows that
that 'a has to denote int. So it behaves as if you had written
let x: (int * int) -> int = fst in (x (0,1), x (0., 1.))
(Personally, I never understood the rationale for that treatment of type
variables. It is one of the things I find more reasonable in SML, where
the equivalent of your example would type-check.)
Cheers,
- Andreas
--
Andreas Rossberg, rossberg@ps.uni-sb.de
Let's get rid of those possible thingies! -- TB
-------------------
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
prev parent reply other threads:[~2004-08-11 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 10:06 fis
2004-08-11 12:17 ` Andreas Rossberg [this message]
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=411A0E73.4060708@ps.uni-sb.de \
--to=rossberg@ps.uni-sb.de \
--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