caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jun Furuse" <jun.furuse@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Recursive module and class
Date: Thu, 10 Jul 2008 09:43:21 -0400	[thread overview]
Message-ID: <5160b4200807100643i2c7dbf0aw2fb681b0745a8ba2@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]

Hi,

Sorry if the following is already a known issue.

The following program trying to define a type and a class mutually recursive
is rejected by ocamlc (3.11+dev12 Private_abbrevs+natdynlink (2008-02-29)):

       module rec M : sig
         type t = Foo of N.c
       end = struct
         type t = Foo of N.c
       end and N : sig
         class c : object method x : M.t end
       end = struct
         class c = object (self)
           method x = M.Foo (self :> c)
         end
       end

The error message is puzzling:

       Error: Signature mismatch:
              Modules do not match:
                sig class c : object method x : M.t end end
              is not included in
                sig class c : object method x : M.t end end
              Type declarations do not match:
                type c = N.c
              is not included in
                type c = < x : M.t >

These signatures are literaly same, but do not match.

The above code is accepted by the compiler if I write

           method x = M.Foo (self :> N.c)

to coerce the object to the outer class N.c instead of c.

Is it a bug of typing? Or is it ok but with a puzzling error message ?

--
Jun FURUSE

[-- Attachment #2: Type: text/html, Size: 2037 bytes --]

             reply	other threads:[~2008-07-10 13:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10 13:43 Jun Furuse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-09 23:32 Jun Furuse

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=5160b4200807100643i2c7dbf0aw2fb681b0745a8ba2@mail.gmail.com \
    --to=jun.furuse@gmail.com \
    --cc=caml-list@yquem.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).