From: Arnaud Spiwack <aspiwack@lix.polytechnique.fr>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Gregory Malecha <gmalecha@gmail.com>,
Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>,
Mailing List OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] "Type constructor b would escape its scope"
Date: Mon, 28 Mar 2016 21:20:55 +0200 [thread overview]
Message-ID: <CAMoPVjePETiJ-9ks=Lq+3U6hWAuqUc_=0MqHS6XQqfVD7xfa2g@mail.gmail.com> (raw)
In-Reply-To: <CAPFanBG6sOSX7r5pavPzsMhTcB1fwSjq36huMXyMNHD5bT=yEA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
On 28 March 2016 at 10:07, Gabriel Scherer <gabriel.scherer@gmail.com>
wrote:
> (* the difference by "(type a) ..." and "type a . ..." is that the latter
> allows polymorphic recursion (just as "'a . ..."), so this example fails
> with just (type a) *)
>
So here's a question which has been nagging me for a while: is there any
occasion where one may prefer to use the `(type a)` or the `'a.` forms over
the `type a.` (apart for syntactical reasons)? If there is I'd be really
interested in seeing an example, for I can't come up with one (especially
for `(type a)`). If there aren't, what are the obstacles to turn the `(type
a)` syntax into a synonymous to the `type a.` syntax? (I'm guessing that
the `'a.` variant would be significantly harder).
[-- Attachment #2: Type: text/html, Size: 1249 bytes --]
next prev parent reply other threads:[~2016-03-28 19:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 6:19 Gregory Malecha
2016-03-27 7:04 ` Leo White
2016-03-27 18:52 ` Gregory Malecha
2016-03-28 1:12 ` Jacques Garrigue
2016-03-28 4:20 ` Gregory Malecha
2016-03-28 8:07 ` Gabriel Scherer
2016-03-28 15:35 ` Gregory Malecha
2016-03-28 19:20 ` Arnaud Spiwack [this message]
2016-03-28 20:51 ` Leo White
2016-03-28 21:00 ` Gerd Stolpmann
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='CAMoPVjePETiJ-9ks=Lq+3U6hWAuqUc_=0MqHS6XQqfVD7xfa2g@mail.gmail.com' \
--to=aspiwack@lix.polytechnique.fr \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=garrigue@math.nagoya-u.ac.jp \
--cc=gmalecha@gmail.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).