caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gregory Malecha <gmalecha@gmail.com>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: Mailing List OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] "Type constructor b would escape its scope"
Date: Sun, 27 Mar 2016 21:20:02 -0700	[thread overview]
Message-ID: <CAGraiHJVq6qMWRWoGNBe4ZPaFfBucoUMb1VuRykRvDbs4USceQ@mail.gmail.com> (raw)
In-Reply-To: <2D2C7D68-D59A-407B-B83A-65622DF9CC25@math.nagoya-u.ac.jp>

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

Thanks. I'm not sure I understand the difference between the two though. Is
there an example showing when they produce different results?

On Sun, Mar 27, 2016 at 6:12 PM, Jacques Garrigue <
garrigue@math.nagoya-u.ac.jp> wrote:

> On 2016/03/28 03:52, Gregory Malecha wrote:
> >
> > Thanks, Leo --
> >
> > This is exactly what I needed to know. I thought that the (type a)
> annotation was forcing the function to be polymorphic. For future
> reference, is there any way to write the annotation (that forces the
> function to be polymorphic) without having to write explicit ‘fun's?
>
> You should either write
>
>   let generic_search_stream : ‘b. int option -> (internal_result, ‘b)
> result_stream = …
>
> or
>
>   let generic_search_stream : type b. int option -> (internal_result, b)
> result_stream = …
>
> where the latter one both requires polymorphism and defines a locally
> abstract type,
> i.e. probably the behavior you expect with (type b).
>
> Jacques
>
>


-- 
gregory malecha

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

  reply	other threads:[~2016-03-28  4:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-27  6:19 Gregory Malecha
2016-03-27  7:04 ` Leo White
2016-03-27 18:52   ` Gregory Malecha
2016-03-28  1:12     ` Jacques Garrigue
2016-03-28  4:20       ` Gregory Malecha [this message]
2016-03-28  8:07         ` Gabriel Scherer
2016-03-28 15:35           ` Gregory Malecha
2016-03-28 19:20           ` Arnaud Spiwack
2016-03-28 20:51             ` Leo White
2016-03-28 21:00             ` Gerd Stolpmann

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=CAGraiHJVq6qMWRWoGNBe4ZPaFfBucoUMb1VuRykRvDbs4USceQ@mail.gmail.com \
    --to=gmalecha@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=garrigue@math.nagoya-u.ac.jp \
    /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).