From: rossberg@ps.uni-sb.de
To: caml-list@inria.fr
Subject: Re: [Caml-list] Recursive module signatures + functors
Date: Tue, 12 Jun 2007 10:51:25 +0200 (CEST) [thread overview]
Message-ID: <62136.84.165.181.142.1181638285.squirrel@www.ps.uni-sb.de> (raw)
In-Reply-To: <Pine.SOL.4.33.0706111848240.11389-100000@loompa.cs.umd.edu>
Michael Furr wrote:
>
> Is this a bug in the type checker or is there a reason that it does not
> unify 't' and 'M.t'?
It is not a bug, but a limitation of the current semantics of recursive
modules. It is unrelated to functors - here is a simpler version of your
example that fails in the same way:
module rec M : sig type t val f : t -> t end =
struct
type t = int
let f (x : M.t) = x
end
It's basically the same issue as described here:
http://caml.inria.fr/pub/ml-archives/caml-list/2007/05/d9414d45a9a6f30f2609e08c43f011a0.en.html
- Andreas
next prev parent reply other threads:[~2007-06-12 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 23:10 Michael Furr
2007-06-12 8:51 ` rossberg [this message]
2007-06-12 9:47 ` [Caml-list] " Xavier Leroy
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=62136.84.165.181.142.1181638285.squirrel@www.ps.uni-sb.de \
--to=rossberg@ps.uni-sb.de \
--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).