caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Mathieu Barbin <mathieu.barbin@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] GADT: question about inference
Date: Fri, 26 Jul 2013 13:15:50 -0400	[thread overview]
Message-ID: <CANXn40m1+bzDuS13_=S3PFmj4h_iz5aZb6fV8PLuuB-Jv_syPg@mail.gmail.com> (raw)

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

Hello,

Playing around with a reduced version of a dynamic types, I ran into some
type errors, and I feel that I'd love to understand more about the way the
inference work:

type _ ty  = Int : int ty | String : string ty

module H : sig
  type t
  val ty : t ty
end = struct
  type t = int
  let ty = Int
end

(* from now, trying various implementation for [f] *)

let f : H.t -> int =
    match H.ty with
    | Int -> (fun (a : H.t) -> (a : int))
    | _ -> assert false
  ;;
Error: This expression has type H.t but an expression was expected of type
         int

let f : H.t -> int = fun (a : H.t) ->
    match H.ty with
    | Int -> (a : int)
    | _ -> assert false
  ;;
Error: This expression has type H.t but an expression was expected of type
         int

let f : H.t -> int =
  let aux : type a. a ty -> a -> int = function
    | Int -> (fun a -> a)
    | _ -> assert false
  in
  aux H.ty
  ;;

(* val f : H.t -> int = <fun> *)

I can't quite come up with a clear mental model of why in-lining the
pattern matching in the first versions of [f]t would not type check. I
tried adding some more type coercions without great success. I'd be very
grateful to get some feed back about this restriction.

Thanks,
Mathieu

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

             reply	other threads:[~2013-07-26 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 17:15 Mathieu Barbin [this message]
2013-07-26 20:27 ` Gabriel Scherer
2013-07-26 21:25   ` Alain Frisch
2013-07-28  0:29     ` Mathieu Barbin

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='CANXn40m1+bzDuS13_=S3PFmj4h_iz5aZb6fV8PLuuB-Jv_syPg@mail.gmail.com' \
    --to=mathieu.barbin@gmail.com \
    --cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).