caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jonathan Protzenko <jonathan.protzenko@gmail.com>
To: Roberto Di Cosmo <roberto@dicosmo.org>,  Ivan Gotovchits <ivg@ieee.org>
Cc: Andreas Rossberg <rossberg@mpi-sws.org>,
	 Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>,
	OCaML List Mailing <caml-list@inria.fr>
Subject: Re: [Caml-list] Equality between abstract type definitions
Date: Fri, 25 Oct 2013 14:45:52 +0200	[thread overview]
Message-ID: <526A6800.9020501@gmail.com> (raw)
In-Reply-To: <20131025123517.GA21960@voyager>

On 10/25/2013 02:35 PM, Roberto Di Cosmo wrote:
> Thanks Ivan,
>        the potential confusion between type annotations
> in the code and type specifications in module interfaces
> is a very good point.
>
> Writing
>
>  let f : 'a -> 'a = fun x -> x+1 
>
> will just boil down to defining 
>
>  val f : int -> int = <fun>
>
> On the other side, declaring 
>
>  val f : 'a -> 'a 
>
> in a module signature actually *requires* the implementation
> to be at least as generic as 'a -> 'a, so a definition
> let f = fun x -> x+1 in the body will not work.
You should also remember that the top-level, which is what most
beginners use, also favors the confusion.

# let f x = x;;
val f : 'a -> 'a = <fun>
# let f : 'a -> 'a = fun x -> x + 1;;
val f : int -> int = <fun>

What OCaml is actually telling you is: "this function has type 'a -> 'a,
but if you write 'a -> 'a yourself, I'm going to give it a totally
different meaning".

~ jonathan

  reply	other threads:[~2013-10-25 12:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24 22:57 Peter Frey
2013-10-24 23:23 ` Jacques Garrigue
2013-10-25  6:44   ` Andreas Rossberg
2013-10-25  8:29     ` Roberto Di Cosmo
2013-10-25  9:59       ` Ivan Gotovchits
2013-10-25 11:09         ` Gabriel Scherer
2013-10-25 14:24           ` Andreas Rossberg
2013-10-25 20:32             ` Yaron Minsky
2013-10-25 20:44               ` Jacques Le Normand
2013-10-26  1:08                 ` Norman Hardy
2013-10-26  5:28                   ` Jacques Garrigue
2013-10-27 12:16               ` Andreas Rossberg
2013-10-27 12:56                 ` Yaron Minsky
2013-10-27 14:28                   ` Gabriel Scherer
2013-10-27 14:43                     ` Yaron Minsky
2013-10-27 15:25                       ` Gabriel Scherer
2013-10-27 15:41                         ` Yaron Minsky
2013-10-25 12:35         ` Roberto Di Cosmo
2013-10-25 12:45           ` Jonathan Protzenko [this message]
2013-10-25 13:20             ` Roberto Di Cosmo
2013-10-25 14:03       ` Andreas Rossberg
2013-10-26  9:07         ` oleg
2013-10-26 14:11           ` Didier Remy
2013-10-26 17:32         ` Didier Remy
2013-10-27 12:07           ` Andreas Rossberg
2013-10-27 14:10             ` Roberto Di Cosmo
2013-10-28  3:30     ` Jacques Garrigue

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=526A6800.9020501@gmail.com \
    --to=jonathan.protzenko@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=garrigue@math.nagoya-u.ac.jp \
    --cc=ivg@ieee.org \
    --cc=roberto@dicosmo.org \
    --cc=rossberg@mpi-sws.org \
    /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).