caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Christopher Zimmermann <christopher@gmerlin.de>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] matching GADT option types
Date: Thu, 17 Jan 2019 11:08:31 +0100	[thread overview]
Message-ID: <20190117110831.7e23a284@mortimer.gmerlin.de> (raw)
In-Reply-To: <CAPFanBEL9Wdb1aYyOBq=VJWcFyZBuRJiFrkkJtX7qPMHWrpdXg@mail.gmail.com>

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

Thank you for the fast answer!

That means my second example will still be rejected in 4.08?

type 'a t =
  | A : [`A] t
  | B : [`A|`B] t

let f =
  fun (type a) ~(p :a t) () -> match p with
    | A -> (A: a t)
    | B -> (B: a t)

let g =
  fun (type a) ~(p :a t option) () -> match p with
    | Some B -> (B: a t)
    | Some A -> (A: a t)
    | None -> (A (* TYPE ERROR HERE *) : a t)

Error: This expression has type [ `A ] t
       but an expression was expected of type a t
       Type [ `A ] is not compatible with type a 


On Thu, 17 Jan 2019 11:12:02 +0100
Gabriel Scherer <gabriel.scherer@gmail.com> wrote:

> Matching on a constructor of a GADT may introduce a typing equation.
> In your example, matching on `A` introduces the equation `a = unit`.
> For this reason, the status of or-patterns (p1 | p2) containing GADT
> constructors is delicate: to type-check them we have to decide which
> equations from both sides are preserved in the result, computing a
> sort of intersection.
> 
> Released versions of OCaml avoid this difficulty by not supporting
> GADTs in or-patterns at all; you have to expand the pattern into two
> branches, as you did in your function `f` above.
> 
> In the current trunk, a change from Thomas Réfis and Leo White has
> been merged that allows GADTs in or-patterns, but discards the
> equations. Your specific example (the function `g`) is now accepted,
> and will be typeable in 4.08. Other examples, where you need to use
> an equation (provided by both sides of the or-patterns) in the body
> of the clause, will still be rejected.
> 
> 
> On Thu, Jan 17, 2019 at 10:46 AM Christopher Zimmermann <
> christopher@gmerlin.de> wrote:  
> 
> > Hi,
> >
> > why does the f type correctly while g fails to type?
> >
> > Christopher
> >
> > type 'a t =
> >   | A : unit t
> >
> > let f =
> >   fun (type a) ~(p :a t option) () -> match p with
> >     | Some A -> ()
> >     | None -> ()
> >
> > let g =
> >   fun (type a) ~(p :a t option) () -> match p with
> >     | Some A (* TYPING ERROR HERE *)
> >     | None -> ()
> >
> > Error: This pattern matches values of type unit t
> >        but a pattern was expected which matches values of type a t
> >        Type unit is not compatible with type a


-- 
http://gmerlin.de
OpenPGP: http://gmerlin.de/christopher.pub
CB07 DA40 B0B6 571D 35E2  0DEF 87E2 92A7 13E5 DEE1

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2019-01-17 10:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17  9:46 Christopher Zimmermann
2019-01-17  9:58 ` Jeremy Yallop
2019-01-17 10:02 ` Christopher Zimmermann
2019-01-17 10:18   ` Gabriel Scherer
2019-01-17 10:12 ` Gabriel Scherer
2019-01-17 10:08   ` Christopher Zimmermann [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=20190117110831.7e23a284@mortimer.gmerlin.de \
    --to=christopher@gmerlin.de \
    --cc=caml-list@inria.fr \
    --cc=gabriel.scherer@gmail.com \
    /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).