From: Vincent Aravantinos <vincent.aravantinos@gmail.com>
To: Anthony Tavener <anthony.tavener@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Nested module exposing type from parent?
Date: Wed, 02 Nov 2011 16:19:39 -0400 [thread overview]
Message-ID: <4EB1A5DB.8070405@gmail.com> (raw)
In-Reply-To: <CAN=ouMSpOuajS2XGtX23M4S73C1XOa4LXZptexk+sh=YsLmauQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2139 bytes --]
Using "include" instead of "open" would work, ie. turning your example into:
module Vec_main = struct
type t = { x: int; y: int }
let make x y = {x;y}
let add a b = {x=a.x+b.x; y=a.y+b.y}
end
module Vec = struct
include Vec_main
module Type = struct
include Vec_main
...
end
end
Then:
# let n = Vec.make 2 5;;
val n : Vec.t = {Vec.x = 2; Vec.y = 5}
# open Vec.Type;;
# let m = {x=1;y=2};;
val m : Vec.Type.t = {x = 1; y = 2}
# Vec.add m n;;
- : Vec.t = {Vec.x = 3; Vec.y = 7}
Cheers
--
Vincent Aravantinos - Postdoctoral Fellow, Concordia University, Hardware Verification Group
On 11/02/2011 03:41 PM, Anthony Tavener wrote:
> I've been struggling with this occasionally...
>
> I'm using nested modules to "open" access to select features of a
> module. My problem is I can't find a way to *expose* types in the
> parent module through such nested modules.
>
> A simplified example of what I'm looking at:
>
> module Vec = struct
>
> type t = { x: int; y: int }
> let make x y = {x;y}
> let add a b = {x=a.x+b.x; y=a.y+b.y}
>
> module Type =
> (* something which has type t = Vec.t,
> * with exposed structure when "open"ed.
> * Also note that Vec is not really an
> * explicit module like this; instead it
> * is implemented in vec.ml <http://vec.ml> *)
> end
>
> Example usage...
>
> let n = Vec.make 2 5
> open Vec.Type
> let m = {x=1;y=2}
> Vec.add m n
>
>
> To date, I've defined the type in the Type submodule, which is then
> used by the parent module. The unsatisfactory quality of this is that
> Vec.Type.t is the "true" type. Ideally the concrete type would live at
> Vec.t, with "open Vec.Type" bringing the fields of the type into scope.
>
> As background, here are examples of opening different features of the
> Vec module:
>
> let c = Vec.add a b
>
> open Vec.Prefixed
> let c = vadd a b
>
> open Vec.Ops
> let c = a +| b
>
> open Vec.Type
> let c = Vec.add a {x;y;z=0.}
>
> Apologies if this is really beginner-list material. It's minor, but
> has been bugging me.
> Thank-you for looking,
>
> Tony
>
[-- Attachment #2: Type: text/html, Size: 4077 bytes --]
next prev parent reply other threads:[~2011-11-02 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 19:41 Anthony Tavener
2011-11-02 20:19 ` Vincent Aravantinos [this message]
[not found] ` <CAN=ouMTApZjpU-CaZtdL4njXtmtRu++7fzJBJL3w3FRcHfjtSA@mail.gmail.com>
[not found] ` <CAN=ouMS9rqqNR3KgCBnnjC_HcMrUnftVw643mkmhC_vrpXfv1A@mail.gmail.com>
2011-11-02 21:14 ` Fwd: " Anthony Tavener
2011-11-02 23:01 ` Gabriel Scherer
2011-11-03 0:06 ` Vincent Aravantinos
2011-11-03 1:03 ` Anthony Tavener
2011-11-03 0:41 ` Martin Jambon
2011-11-03 1:04 ` Anthony Tavener
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=4EB1A5DB.8070405@gmail.com \
--to=vincent.aravantinos@gmail.com \
--cc=anthony.tavener@gmail.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