caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Dawid Toton <d0@wp.pl>
Cc: Caml <caml-list@inria.fr>
Subject: Re: [Caml-list] When functor yields many types - include a module with extra type equality?
Date: Tue, 3 Apr 2012 14:40:21 +0200	[thread overview]
Message-ID: <CAPFanBHX8y7YXB41fMc9O2+5XOb+=y_82A36yBQVehFNZB-jnA@mail.gmail.com> (raw)
In-Reply-To: <4F7ADDAF.2030201@wp.pl>

I learned a clever hack from Jacques Garrigue: recursive modules allow
you to get a module corresponding to a module type. The "module of S"
is
  module rec X : S = X

Using this trick, one can write in c_sig.ml

  module type S = sig
    ...
  end

the usual thing in .mli, and then

  module Make (B : B) = struct
    module rec S_mod : (Sig.S with type t = B.t) = S_mod
    include S_mod
    let not_much_code = assert false
  end

On Tue, Apr 3, 2012 at 1:23 PM, Dawid Toton <d0@wp.pl> wrote:
> Consider the following:
>
> --- a.mli
> module type B = sig
>  type t
> end
>
> module type S = sig
>  type t
>  type other_lenghty_definitions
>  val not_much_code : t
> end
>
> module Make (B : B) : S
>  with type t = B.t
> ---
> --- a.ml
> module type B = sig
>  type t
> end
>
> module type S = sig
>  type t
>  type other_lenghty_definitions
>  val not_much_code : t
> end
>
> module Make (B : B) = struct
>  type t = B.t
>  type other_lenghty_definitions
>  let not_much_code = assert false
> end
> ---
>
> So we have to keep 3 copies of other_lenghty_definitions. I can have it
> isolated in a separate file and insert into a.ml and a.mli in an extra
> preprocessing step. But I believe there should be some clean solution,
> something like the following:
>
> --- c_sig.ml
> module S = struct
>  type t
>  type other_lenghty_definitions
> end
>
> module type S = sig
>  include (module type of S) (* 1 *)
>  val not_much_code : t
> end
> ---
> --- c.mli
> module type B = sig
>  type t
> end
>
> module Make (B : B) : C_sig.S
>  with type t = B.t
> ---
> --- c.ml
> module type B = sig
>  type t
> end
>
> module Make (B : B) = struct
>  include C_sig.S
>    with type t = B.t (* 2 *)
>
>  let not_much_code = assert false
> end
> ---
>
> How to do what I mark with (* 1 *) and (* 2 *) correctly? Would it help if I
> upgrade my toolchain from 3.11.2 to some more recent version?
> Dawid
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>


  reply	other threads:[~2012-04-03 12:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03 11:23 Dawid Toton
2012-04-03 12:40 ` Gabriel Scherer [this message]
2012-04-03 17:54 ` Hezekiah M. Carty

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='CAPFanBHX8y7YXB41fMc9O2+5XOb+=y_82A36yBQVehFNZB-jnA@mail.gmail.com' \
    --to=gabriel.scherer@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=d0@wp.pl \
    /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).