From: Peng Zang <peng.zang@gmail.com>
To: caml-list@inria.fr
Subject: specifying the type of an argument with more than one #classpath
Date: Wed, 5 Mar 2008 20:52:06 -0500 [thread overview]
Message-ID: <200803052052.10651.peng.zang@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I am aware that when specifying the type of an argument to a function, one can
use the "#classpath" notation to specify "any subtype of classpath".
Eg:
class type foo = object
method foo : string
end;;
# let takesomefoo (x:#foo) = x;;
val takesomefoo : (#foo as 'a) -> 'a = <fun>
However, I cannot figure out how to specify more than one such constraint.
Eg. I want to specify an argument that is foo-able and bar-able like this:
class type bar = object
method bar : string
end
# 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? I am familiar with class definitions which allow you to do
this:
class ['a] foobar (x:'a) = object
constraint 'a = #foo
constraint 'a = #bar
method getx = x
end;;
But I don't see how to specify such constraints in a normal function on the
type of an argument.
Is there some simple trick people have found for specifying various type
constraints on arguments?
Thanks in advance,
Peng
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
iD8DBQFHz05KfIRcEFL/JewRAjD4AJ9hexh+HUP5h2aavCbCXWR8JoVReQCePBBz
FIXqFDT3NEhLgtQZwrU7E54=
=qonr
-----END PGP SIGNATURE-----
next reply other threads:[~2008-03-06 1:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 1:52 Peng Zang [this message]
2008-03-06 1:56 ` [Caml-list] " Edgar Friendly
2008-03-06 2:04 ` Peng Zang
2008-03-06 2:16 ` Eric Cooper
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=200803052052.10651.peng.zang@gmail.com \
--to=peng.zang@gmail.com \
--cc=caml-list@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