From: Philippe Veber <philippe.veber@googlemail.com>
To: caml-list@yquem.inria.fr
Subject: Commuting labeled arguments
Date: Sat, 14 Mar 2009 11:14:46 +0100 [thread overview]
Message-ID: <721f7f5a0903140314saf947b9n1531207146ba2e29@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
Hi all,
is this behaviour of the type checker expected ?
Objective Caml version 3.11.0
# let f g x y = g ~x ~y;;
val f : (x:'a -> y:'b -> 'c) -> 'a -> 'b -> 'c = <fun>
# let g ~y ~x = x + y;;
val g : y:int -> x:int -> int = <fun>
# f g;;
Error: This expression has type y:int -> x:int -> int
but is here used with type x:'a -> y:'b -> 'c
If so, I'm tempted to fill a report to mantis anyway, to get this said in
the manual (i've not seen anything for this case, but i might have missed
something).
Philippe.
[-- Attachment #2: Type: text/html, Size: 694 bytes --]
next reply other threads:[~2009-03-14 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 10:14 Philippe Veber [this message]
2009-03-14 14:43 ` [Caml-list] " Martin Jambon
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=721f7f5a0903140314saf947b9n1531207146ba2e29@mail.gmail.com \
--to=philippe.veber@googlemail.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).