From: "Jacques.Garrigue" <jacques.garrigue@gmail.com>
To: "Norm Hardy" <norm@ootbcomp.com>, "Caml List" <caml-list@inria.fr>
Subject: Re: [Caml-list] GADTs in the manual
Date: Sun, 6 Jan 2013 09:07:02 +0900 [thread overview]
Message-ID: <75D5C8372DD3427FA865B97E9A9C4062@VAIO> (raw)
In-Reply-To: <13EC7FF3-880B-414A-AEDB-8DDC1516D651@att.net>
Documentation bugs also go to the bug tracking system, in the "OCaml
documentation" category.
http://caml.inria.fr/mantis/bug_report_page.php
> It seems clear to me that the subtext “| Add : (int -> int -> int) term”
> is meant to be a constr-decl but none of the three alternative forms
> produce that. The alternative, new with GADTs, requires a ->.
Right, there is a missing production:
constr-name : typexpr
for constructors without arguents.
> In the explanatory text there is the phrase “where type parameters are
> instantiated” which I do not understand.
This means that the type parameters may be more specific than in the generic
case.
For instance int term is more specific than 'a term.
Jacques Garrigue
-----Original Message-----
From: Norman Hardy
Sent: Sunday, January 06, 2013 2:56 AM
To: Caml List
Subject: [Caml-list] GADTs in the manual
Where do I report suspected errors in the manual?
I think that the first example does not comply with the extended syntax.
See
http://cap-lore.com/Languages/ocaml/bb.html
since I don't know how to reliably insert links into e-mail.
--
Caml-list mailing list. Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs
prev parent reply other threads:[~2013-01-06 0:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 17:56 Norman Hardy
2013-01-06 0:07 ` Jacques.Garrigue [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=75D5C8372DD3427FA865B97E9A9C4062@VAIO \
--to=jacques.garrigue@gmail.com \
--cc=caml-list@inria.fr \
--cc=norm@ootbcomp.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).