caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jeremy Yallop <j.d.yallop@sms.ed.ac.uk>
To: caml-list@inria.fr
Cc: brogoff <brogoff@speakeasy.net>, Luc Maranget <luc.maranget@inria.fr>
Subject: Re: [Caml-list] Oddness with recursive polymorphic variants
Date: Thu, 04 May 2006 19:58:31 +0100	[thread overview]
Message-ID: <445A4ED7.9080900@sms.ed.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.0605041128440.9940@shell3.speakeasy.net>

brogoff wrote:
> On Thu, 4 May 2006, Luc Maranget wrote:
> 
>>I cannot really explain why it matters, but I can supply a minimal (?) example
>>
>>type f = [`A ]
>>type g = [f | `C]
>>
>>let k (x:f) = (x:g);;
>>               ^
>>This expression has type f but is here used with type g
>>The first variant type does not allow tag(s) `C
> 
> 
> Not enough polymorphism, the error message seems clear
> 
> type 'a h = 'a constraint 'a = [> `A];;
> let k (x : 'a h) = (x : g)

Thanks for the reply.  That doesn't seem to be what I want, though.  The 
input to k should have type 'f'.  The output should have type 'g'.  Your 
'k' can be called with values that don't match type 'f':

    # k `C;;
    - : g = `C

The following does what I want:

    let k (#f as x:f) = (x:g)

I'd like to understand why it behaves differently from the following:

    let k (x:f) = (x:g)

Jeremy.


  reply	other threads:[~2006-05-04 22:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04 15:54 Jeremy Yallop
2006-05-04 17:10 ` [Caml-list] " Luc Maranget
2006-05-04 18:26   ` Michael Wohlwend
2006-05-04 18:33   ` brogoff
2006-05-04 18:58     ` Jeremy Yallop [this message]
2006-05-05  0:01       ` brogoff
2006-05-05  6:43         ` Luc Maranget
  -- strict thread matches above, loose matches on Subject: below --
2006-05-04 15:50 Jeremy Yallop
2006-05-04 19:03 ` [Caml-list] " Nils Gesbert
2006-05-04 20:30   ` Nils Gesbert
2006-05-05  8:04   ` Jeremy Yallop

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=445A4ED7.9080900@sms.ed.ac.uk \
    --to=j.d.yallop@sms.ed.ac.uk \
    --cc=brogoff@speakeasy.net \
    --cc=caml-list@inria.fr \
    --cc=luc.maranget@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).