From: Keiko Nakata <keiko@kurims.kyoto-u.ac.jp>
To: Julien.Signoles@lri.fr
Cc: johannes.kanig@lri.fr, caml-list@inria.fr
Subject: Re: [Caml-list] polymorphic variants and promotion
Date: Tue, 19 Feb 2008 22:37:59 +0900 (JST) [thread overview]
Message-ID: <20080219.223759.125111280.keiko@kurims.kyoto-u.ac.jp> (raw)
In-Reply-To: <Pine.LNX.4.63.0802191330150.23713@serveur9-10.lri.fr>
Hello,
indeed we need to use double coercion, instead of single:
# ((`A 1 : [ `A of int ]) : [ `A of int ] :> [> `A of int ]);;
- : [> `A of int ] = `A 1
# ((`A 1 : [ `A of int ]) :> [> `A of int ]);;
- : [ `A of int ] = `A 1
This explains a little to me about the differences
between double and single coercions.
Thanks.
With best,
Keiko
next prev parent reply other threads:[~2008-02-19 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 10:23 Johannes Kanig
2008-02-19 12:38 ` [Caml-list] " Julien Signoles
2008-02-19 13:37 ` Keiko Nakata [this message]
2008-02-19 22:26 ` Christophe Raffalli
2008-02-20 4:50 ` Jacques Garrigue
2008-02-19 12:48 ` Remi Vanicat
2008-02-20 5:01 ` [Caml-list] " Jacques Garrigue
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=20080219.223759.125111280.keiko@kurims.kyoto-u.ac.jp \
--to=keiko@kurims.kyoto-u.ac.jp \
--cc=Julien.Signoles@lri.fr \
--cc=caml-list@inria.fr \
--cc=johannes.kanig@lri.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).