From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] annotations and type-checking
Date: Wed, 29 Jul 2009 20:01:02 +0100 [thread overview]
Message-ID: <200907292001.02773.jon@ffconsultancy.com> (raw)
In-Reply-To: <20090729.233928.59476910.garrigue@math.nagoya-u.ac.jp>
On Wednesday 29 July 2009 15:39:28 Jacques Garrigue wrote:
> Because it is useful to be able to have type annotations sharing type
> variables in different places in a term (for instance for different
> arguments).
That's very interesting. I had taken this for granted and never noticed this
subtlety before...
--
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e
prev parent reply other threads:[~2009-07-29 17:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 21:47 Aaron Bohannon
2009-07-28 23:28 ` [Caml-list] " Jon Harrop
2009-07-28 23:04 ` Philippe
2009-07-29 5:38 ` Johannes Kanig
2009-07-29 7:40 ` Mark Shinwell
2009-07-29 13:41 ` Aaron Bohannon
2009-07-29 14:39 ` Jacques Garrigue
2009-07-29 16:50 ` Aaron Bohannon
2009-07-29 19:01 ` Jon Harrop [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=200907292001.02773.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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).