From: Roberto Di Cosmo <roberto@dicosmo.org>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: Gabriel Scherer <gabriel.scherer@gmail.com>, caml-list@inria.fr
Subject: Re: [Caml-list] Funny name for a type variable in the output: should this be filed on the BTS?
Date: Fri, 23 Mar 2012 09:13:35 +0100 [thread overview]
Message-ID: <20120323081335.GA27190@voyager> (raw)
In-Reply-To: <8F5F6351-7DF3-4BFD-BE79-6B76696A457C@math.nagoya-u.ac.jp>
Dear Jacques,
that seems a perfect fix, for me, as it also gives a hint
to the user about what is going on under the hood, thanks for
implementing it so fast.
And thanks to all for the feedback on this issue :-)
--Roberto
On Fri, Mar 23, 2012 at 03:45:51PM +0900, Jacques Garrigue wrote:
<snip>
> The point here is that the "type a b. ..." syntax is syntactic sugar.
> Rather than putting efforts in making it "hygienic", at the cost of
> mangling type variable names, isn't it simpler to define precisely
> how it expands, and prohibit ambiguous types?
> I would argue that this is actually simpler to explain it that way
> (if you want to give an exact specification).
>
> I have committed this in trunk and 4.00, and the output now is a syntax
> error:
>
> Error: In this scoped type, variable 'a is reserved for the local type a.
>
<snip>
>
> Jacques Garrigue
next prev parent reply other threads:[~2012-03-23 8:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 9:51 Roberto Di Cosmo
2012-03-22 12:05 ` Julien Signoles
2012-03-22 13:39 ` Jonathan Protzenko
2012-03-22 14:40 ` Didier Remy
2012-03-22 22:12 ` Jacques Garrigue
2012-03-22 23:35 ` Roberto Di Cosmo
2012-03-23 5:52 ` Gabriel Scherer
2012-03-23 6:45 ` Jacques Garrigue
2012-03-23 8:13 ` Roberto Di Cosmo [this message]
2012-03-23 10:25 ` Gabriel Scherer
2012-03-24 0:24 ` 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=20120323081335.GA27190@voyager \
--to=roberto@dicosmo.org \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=garrigue@math.nagoya-u.ac.jp \
/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