caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
To: brian-l-smith@uiowa.edu
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Syntax for multiple subtyping constraints?
Date: Fri, 12 Jul 2002 17:54:16 +0900	[thread overview]
Message-ID: <20020712175416Y.garrigue@kurims.kyoto-u.ac.jp> (raw)
In-Reply-To: <3D2E6A3F.70001@uiowa.edu>

From: Brian Smith <brian-l-smith@uiowa.edu>

> Please consider the following:
> 
> # class virtual x = object method virtual foo : int    end
>    class virtual y = object method virtual bar : string end
>    class z =
>      object
>       method foo = 2
>       method bar = "there"
>      end;;
> 
> How can I assert that class "z" is supposed to be a subtype of class x 
> and class y? In other words, how can I assert that (some_z : z :> x) and 
> (some_z : z :> y) will always be valid?

You have many ways to force (self : #x) and (self : #y).

class z = object ((self : #x) : #y)
  method foo = 2
  method bar = "there"
end
class z = object (self : 'a)
  constraint 'a = #x
  constraint 'a = #y
  method foo = 2
  method bar = "there"
end
class z = object
  inherit x
  inherit y
  method foo = 2
  method bar = "there"
end

The last one uses the fact x and y are virtual classes, rather than
class types.

Note that none of these guarantee a subtyping relation, only a
matching one. Fortunately, as long as the type of self does not appear
in a contravariant position in x or y, this relation is included in
subtyping.

Jacques Garrigue
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2002-07-12  8:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-12  5:33 Brian Smith
2002-07-12  8:54 ` Jacques Garrigue [this message]
2002-07-12 13:21 ` John Max Skaller

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=20020712175416Y.garrigue@kurims.kyoto-u.ac.jp \
    --to=garrigue@kurims.kyoto-u.ac.jp \
    --cc=brian-l-smith@uiowa.edu \
    --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;
as well as URLs for NNTP newsgroup(s).