From: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
To: David.Monniaux@ens.fr
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] module types and polymorphic variants
Date: Thu, 31 Jan 2002 08:52:01 +0900 [thread overview]
Message-ID: <20020131085201L.garrigue@kurims.kyoto-u.ac.jp> (raw)
In-Reply-To: <Pine.GSO.4.03.10201301743140.13661-100000@basilic.ens.fr>
From: David Monniaux <David.Monniaux@ens.fr>
> I tried the following:
>
> module type MT =
> sig
> type t
> val f: t->int
> end with type t = 'x constraint 'x = [> `A];;
>
> ocaml gives me:
> module type MT = sig type t = [> `A] val f : t -> int end
This is already strange. Probably a bug: the definition of t should
not be accepted. Or is it ok because this is only an abstract
signature, not the signature of an actual module ?
> but this latter definition is NOT accepted by OCaml:
> "Unbound type parameter [..]"
That seems more reasonable :-)
> module N (M : MT) =
> struct
> type t = [M.t | `B]
> let f: t->int = function
> `B -> 1
> | x -> M.f x
> end;;
>
> The functor definition is refused because
> "The type M.t is not a polymorphic variant type"
>
> Is there a workaround?
Not that I know. Polymorphic variant extension only works for known
closed variant types, otherwise it would not be sound.
Note that all the above code would work if you defined type t = [ `A ]
to begin with, but this is probably not what you want.
# module type MT =
sig
type t = [ `A ]
val f: t->int
end;;
module type MT = sig type t = [ `A] val f : t -> int end
# module N (M : MT) =
struct
type t = [M.t | `B]
let f: t->int = function
`B -> 1
| #M.t as x -> M.f x
end;;
module N : functor (M : MT) -> sig type t = [ `A | `B] val f : t -> int end
For incremental extension of an unknown type, you must use a disjoint
sum. The coalesced sum provided by polymorphic variant extension will
not work.
module type MT = sig type t val f : t -> int end;;
module N (M : MT) =
struct
type t = [ `Inh of M.t | `B ]
let f: t->int = function
`B -> 1
| `Inh x -> M.f x
end;;
Theoretical thought: some other frameworks based on extensible rows
would allow what your write, but I'm starting to think that what they
provide is not coalesced sum, but rather a flattened form of disjoint
sum. Nice for some things, but harder to reason about for others.
Jacques Garrigue
-------------------
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
prev parent reply other threads:[~2002-01-31 1:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 16:46 David Monniaux
2002-01-30 23:52 ` Jacques Garrigue [this message]
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=20020131085201L.garrigue@kurims.kyoto-u.ac.jp \
--to=garrigue@kurims.kyoto-u.ac.jp \
--cc=David.Monniaux@ens.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