From: Remi Vanicat <remi.vanicat@laposte.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Documentation error - #myvariant
Date: Thu, 29 Apr 2004 14:40:37 +0200 [thread overview]
Message-ID: <8765bjvtx6.dlv@vanicat.homelinux.org> (raw)
In-Reply-To: <E1BJ9Z8-0005Rl-00@mta1.cl.cam.ac.uk> (Keith Wansbrough's message of "Thu, 29 Apr 2004 12:18:54 +0100")
Keith Wansbrough <Keith.Wansbrough@cl.cam.ac.uk> writes:
> Hi.. the OCaml documentation, section 4.2 on polymorphic variants,
> Advanced use, explains that
>
> To make this even more confortable, you may use type definitions as
> abbreviations for or-patterns. That is, if you have defined type
> myvariant = [`Tag1 int | `Tag2 bool], then the pattern #myvariant is
> equivalent to writing (`Tag1(_ : int) | `Tag2(_ : bool)).
>
> But this is not correct! Consider
>
> type de = [`D | `E of de];;
>
> type def = [`D | `E of def | `F of def];;
>
> let rec deproc2 rfun =
> function
> | `D -> print_string "D"; `D
> | `E(x) -> print_string "E"; `E(rfun x)
>
> let rec deproc3 x = deproc2 deproc3 x
>
> let rec defproc2 rfun =
> function
> (* | (`D | `E(_)) as x -> deproc2 rfun x *)
> | #de as x -> deproc2 rfun x
> | `F(x) -> print_string "f"; `F(rfun x)
If I read the documentation, this is rewrote as
let rec defproc2 rfun =
function
| (`D | `E(_:de)) as x -> deproc2 rfun x
| `F(x) -> print_string "f"; `F(rfun x)
that mean that what is in the `E must be a de, not a def. There is
your error.
In fact, your code will do what you want if you don't define your type
as recursive but as polymorphic :
type 'a de = [`D | `E of 'a];;
type 'a def = [`D | `E of 'a | `F of 'a];;
then, your code will work as expected. Well, the last definition became :
let rec defproc3 : ('a def as 'a) -> 'a =
fun x -> defproc2 defproc3 x
There is a very interesting
example about this in the ocaml source : ocaml/testlabl/mixin.ml
[...]
> as expected. It looks to me like #de means (`D | `E(_:de)), rather
> than (`D | `E(_)) as I expected; except that I'm not even sure what
> `E(_:de) means in this case - does it do type-directed matching at
> runtime?
no, it is a constraint on the type of what is the `E done at compile
time. And it is the source of your error because a de is not a def.
>
> Could the documentation please be made more accurate at this point?
>
The documentation is accurate.
--
Rémi Vanicat
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-04-29 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 11:18 Keith Wansbrough
2004-04-29 12:40 ` Remi Vanicat [this message]
2004-04-29 13:54 ` Keith Wansbrough
2004-04-29 18:09 ` skaller
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=8765bjvtx6.dlv@vanicat.homelinux.org \
--to=remi.vanicat@laposte.net \
--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).