From: Gabriel Kerneis <kerneis@pps.jussieu.fr>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Why type inference fails in this code
Date: Fri, 9 Oct 2009 10:59:16 +0200 [thread overview]
Message-ID: <20091009085916.GB6397@kerneis.info> (raw)
In-Reply-To: <20091009084135.GA6397@kerneis.info>
On Fri, Oct 09, 2009 at 10:41:35AM +0200, Gabriel Kerneis wrote:
> Yes, sorry, I should have checked before posting since I always get it
> wrong, confusing forall and exists.
And just in case someone else on this list does not understand (or
remember) the difference, he should read the following thread:
http://caml.inria.fr/pub/ml-archives/caml-list/2007/05/08f6ca7a2c045d2801f2a2cc0ae8aa63.en.html
Enlighting!
--
Gabriel
next prev parent reply other threads:[~2009-10-09 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 5:25 rouanvd
2009-10-09 6:54 ` [Caml-list] " Vincent Aravantinos
2009-10-09 7:09 ` Gabriel Kerneis
2009-10-09 8:22 ` Virgile Prevosto
2009-10-09 8:41 ` Gabriel Kerneis
2009-10-09 8:59 ` Gabriel Kerneis [this message]
2009-10-09 10:22 ` Jeremy Yallop
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=20091009085916.GB6397@kerneis.info \
--to=kerneis@pps.jussieu.fr \
--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).