caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Remi VANICAT <vanicat@labri.u-bordeaux.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Allowing many types
Date: 11 Feb 2002 12:48:05 +0100	[thread overview]
Message-ID: <87u1soz1ca.dlv@wanadoo.fr> (raw)
In-Reply-To: <20020211105306.GC11294@mandelbrot.house>

Ceri Storey <cez@pkl.net> writes:

> On Sun, Feb 10, 2002 at 08:43:20PM -0500, Ryan Tarpine wrote:
> > Is there a type that means "any polymorphic variant"?  Trying to set
> >  type primitive = [ `PTest ]
> > forces only `PTest to be the value of object_data.  How can I allow 
> > anything to be stored there?
> 
> According to the output of the toplevel, then the type [> `Foo | `Bar ]
> should be usable, but alas, it is not allowable in type specifictions,
> giving "Unbound type parameter [..]". 
> 
> I've also tried just using plain tuples for this, but then lots of types
> become ungeneralisable, eg in the trivial example:
> # List.map (fun x -> x) [`X; `Y; `Z];;
> - : _[> `X | `Y | `Z] list = [`X; `Y; `Z]
> 
> So say, declaring such a variable in a complied module is impossible
> (AFAIK). 

there is a hidden type variable :

type 'a t = 'a constraint 'a = [> `Foo | `Bar ]

work...


-- 
Rémi Vanicat
vanicat@labri.u-bordeaux.fr
http://dept-info.labri.u-bordeaux.fr/~vanicat
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  reply	other threads:[~2002-02-11 11:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-11  1:43 Ryan Tarpine
2002-02-11 10:53 ` Ceri Storey
2002-02-11 11:48   ` Remi VANICAT [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-08  2:29 Ryan Tarpine
2002-02-08 16:37 ` Ceri Storey
2002-02-08 16:53   ` Remi VANICAT
2002-02-10 17:42     ` Ceri Storey

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=87u1soz1ca.dlv@wanadoo.fr \
    --to=vanicat@labri.u-bordeaux.fr \
    --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).