caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jeff Meister <nanaki@gmail.com>
To: Leo White <lpw25@cam.ac.uk>
Cc: Matej Kosik <5764c029b688c1c0d24a2e97cd764f@gmail.com>,
	OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] strange typechecking result
Date: Fri, 22 Feb 2013 15:09:41 -0800	[thread overview]
Message-ID: <CAHaHOqRY55cUFeou=qe96d2AOsNqBWj3_qazJoYxYevMhsGBtg@mail.gmail.com> (raw)
In-Reply-To: <Prayer.1.3.5.1302222106030.20720@hermes-1.csi.cam.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]

As I understand it, polymorphic recursive functions require type
annotations because inferring their types is undecidable in the general
case.


On Fri, Feb 22, 2013 at 1:06 PM, Leo White <lpw25@cam.ac.uk> wrote:

> I would like to ask:
>>
>> - Where is that restriction explained?
>>   (I've searched Ocaml reference manual for "monomorphic" but nothing
>>    relevant seemed to come up)
>>
>> - Where are things like:
>>
>>      'a. 'a -> unit
>>
>>   described?
>>
>>
> I'm not sure if the restriction is explained anywhere but the solution is
> described in:
>
>  http://caml.inria.fr/pub/docs/**manual-ocaml-4.00/manual021.**html#toc79<http://caml.inria.fr/pub/docs/manual-ocaml-4.00/manual021.html#toc79>
>
> Regards,
>
> Leo
>
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/**arc/caml-list<https://sympa.inria.fr/sympa/arc/caml-list>
> Beginner's list: http://groups.yahoo.com/group/**ocaml_beginners<http://groups.yahoo.com/group/ocaml_beginners>
> Bug reports: http://caml.inria.fr/bin/caml-**bugs<http://caml.inria.fr/bin/caml-bugs>
>

[-- Attachment #2: Type: text/html, Size: 1836 bytes --]

      reply	other threads:[~2013-02-22 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-22 17:50 Matej Kosik
2013-02-22 18:33 ` Leo White
2013-02-22 20:14   ` Matej Kosik
2013-02-22 21:06     ` Leo White
2013-02-22 23:09       ` Jeff Meister [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='CAHaHOqRY55cUFeou=qe96d2AOsNqBWj3_qazJoYxYevMhsGBtg@mail.gmail.com' \
    --to=nanaki@gmail.com \
    --cc=5764c029b688c1c0d24a2e97cd764f@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=lpw25@cam.ac.uk \
    /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).