From: Michael Vanier <mvanier@cs.caltech.edu>
To: pierre.weis@inria.fr
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] simple typing question
Date: Tue, 2 Jul 2002 02:49:26 -0700 [thread overview]
Message-ID: <200207020949.g629nQ606959@orchestra.cs.caltech.edu> (raw)
In-Reply-To: <200207020914.LAA16152@pauillac.inria.fr> (message from Pierre Weis on Tue, 2 Jul 2002 11:14:58 +0200 (MET DST))
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2142 bytes --]
> From: Pierre Weis <pierre.weis@inria.fr>
> Date: Tue, 2 Jul 2002 11:14:58 +0200 (MET DST)
> Cc: caml-list@inria.fr
> Content-Type: text/plain; charset=ISO-8859-1
>
> >
> > I imagine this has been asked and answered before, so I apologize in
> > advance.
> >
> > Compare these two functions:
> >
> > # let f x = List.map (fun y -> y) x ;;
> > val f : 'a list -> 'a list = <fun>
> >
> > and
> >
> > # let f = List.map (fun y -> y) ;;
> > val f : '_a list -> '_a list = <fun>
> >
> > Why does the second use the '_a type variable instead of 'a? I thought
> > that special type variables only had to do with polymorphic references.
> > The FAQ states that the latter expression can't be generalized, but I don't
> > really understand why.
> >
> > Mike
>
> This is explained in the FAQ of the language either in english
>
> http://pauillac.inria.fr/caml/FAQ/FAQ_EXPERT-eng.html#polymorphisme
>
> ou en français:
>
> http://pauillac.inria.fr/caml/FAQ/FAQ_EXPERT-fra.html#polymorphisme
>
> If you don't understand the explanations, please let me know.
>
> Cordialement,
>
> Pierre Weis
>
> INRIA, Projet Cristal, Pierre.Weis@inria.fr, http://pauillac.inria.fr/~weis/
>
>
>
I *almost* understand. I understand the need for restrictions with
polymorphic references. The stated rule is that for
let name = expr1 ...
The type of expr1 is generalized when expr1 is a function, an identifier
or a constant. Otherwise the identifier name is not polymorphic (type
variables are not generalized).
And later it's stated that when expr1 is "map (function x -> x)" it's an
application, so it isn't generalized. However, it's an application that
evaluates to a function, so it seems like it would meet the stated
criteria. Also, I'm not sure why such a restrictive rule is needed. If
expr1 doesn't manipulate references, why can't it be generalized? Sorry to
belabor this.
Mike
-------------------
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-07-02 11:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-02 4:14 Michael Vanier
2002-07-02 9:14 ` Pierre Weis
2002-07-02 9:49 ` Michael Vanier [this message]
2002-07-02 11:29 ` Daniel de Rauglaudre
2002-07-02 11:42 ` Xavier Leroy
2002-07-02 18:57 ` Pixel
2002-07-02 20:59 ` Pierre Weis
2002-07-03 0:39 ` Pixel
2002-07-03 1:49 ` Jacques Garrigue
2002-07-03 23:24 ` Pixel
2002-07-03 7:51 ` Francois Pottier
2002-07-03 11:25 ` Pixel
2002-07-03 18:10 ` Lauri Alanko
2002-07-02 14:56 ` 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=200207020949.g629nQ606959@orchestra.cs.caltech.edu \
--to=mvanier@cs.caltech.edu \
--cc=caml-list@inria.fr \
--cc=pierre.weis@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