From: Eric Cooper <ecc@cmu.edu>
To: caml-list@yquem.inria.fr, caml-list@inria.fr
Subject: Re: [Caml-list] specifying the type of an argument with more than one #classpath
Date: Wed, 5 Mar 2008 21:16:30 -0500 [thread overview]
Message-ID: <20080306021630.GB14754@stratocaster.home> (raw)
In-Reply-To: <200803052052.10651.peng.zang@gmail.com>
On Wed, Mar 05, 2008 at 08:52:06PM -0500, Peng Zang wrote:
> # let takesomefooable_and_barable (x:#foo #bar) = x;;
> The type constructor bar expects 0 argument(s),
> but is here applied to 1 argument(s)
>
>
> Which shows I'm clearly not syntactically expressing this correctly. I
> checked the manual and it doesn't seem possible... How do I do this or
> workaround it?
You were very close:
# let f ((x : #foo) : #bar) = x;;
val f : (< bar : string; foo : string; .. > as 'a) -> 'a = <fun>
--
Eric Cooper e c c @ c m u . e d u
next prev parent reply other threads:[~2008-03-06 2:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 1:52 Peng Zang
2008-03-06 1:56 ` [Caml-list] " Edgar Friendly
2008-03-06 2:04 ` Peng Zang
2008-03-06 2:16 ` Eric Cooper [this message]
2008-03-06 12:02 ` Peng Zang
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=20080306021630.GB14754@stratocaster.home \
--to=ecc@cmu.edu \
--cc=caml-list@inria.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).