caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yaron Minsky <yminsky@janestreet.com>
To: caml-list@inria.fr
Subject: [Caml-list] "with module" surprises
Date: Mon, 9 May 2011 10:27:02 -0400	[thread overview]
Message-ID: <20110509142702.GZ28842@janestreet.com> (raw)

I've gotten bitten recently by the semantics of "with module", and after
getting an explanation about how this seems to work in OCaml, I'm now
deeply confused.  Here's the example I was shown:

  module M = struct
    let x = 13
  end

  module type S = sig
    module M' : sig end
  end
  with module M' = M

The inferred types for this will be:

  module M : sig val x : int end
  module type S = sig module M' : sig val x : int end end

Whereas I would have expected this:

  module M : sig val x : int end
  module type S = sig module M' : sig end end

In other words, the "with module" constraint has added new structure to
the signature S, rather than just adding constraints.  This strikes me
as deeply strange, and indeed, has caused a bunch of head-scratching
here when using "with module".  Is this a bug?  Or is this really the
desired semantics.  My understanding is that in SML, "with module"
simply adds in a bunch of type-level sharing constraints.  From that
point of view, this behavior is pretty surprising.

Not only that, it's what the OCaml manual says.  From section 6.10.4

  The constraint [module module-path = extended-module-path] adds type
  equations to all type components of the sub-structure denoted by
  [module-path], making them equivalent to the corresponding type
  components of the structure denoted by [extended-module-path].
      
y

-- 
Yaron Minsky

             reply	other threads:[~2011-05-09 14:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 14:27 Yaron Minsky [this message]
2011-05-09 15:12 ` Markus Mottl
2011-05-09 16:26   ` Yaron Minsky
2011-05-09 17:21     ` Markus Mottl
2011-05-09 17:33       ` Andreas Rossberg
2011-05-09 18:56         ` Markus Mottl

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=20110509142702.GZ28842@janestreet.com \
    --to=yminsky@janestreet.com \
    --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).