From: Yitzhak Mandelbaum <yitzhak@research.att.com>
To: caml-list@yquem.inria.fr
Subject: "opening" record types
Date: Tue, 21 Aug 2007 09:18:02 -0400 [thread overview]
Message-ID: <67ECB685-E69A-43CA-867D-30B879DB0510@research.att.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
Hi,
I'm generally averse to opening modules, as I find it can make it
hard to figure out where definitions are coming from. Instead, I
prefer to bind only those pieces of the module that I need, and to do
so explicitly. However, there is one instance in which I find myself
with little choice: record types. In order to bind the field-
constructors for a record, you need to copy the entire type from the
module in which its declared. For example,
module Foo =
struct
type t = {a: int; b:int}
end
without copying the type:
let y = {Foo.a=3; Foo.b=4}
with copying:
type t = Foo.t = {a: int; b:int}
let x = {a=3; b=4}
While this is a nuisance to begin with, its even worse if the record
type is subject to change -- each time it changes, you need to update
every place where you copied the definition.
Is there any way around this? That is, is there any way to use the
field names of a record defined in another module without opening the
whole module or copying the whole definition of the record.
Cheers,
Yitzhak
--------------------------------------------------
Yitzhak Mandelbaum
AT&T Labs - Research
http://www.research.att.com/~yitzhak
[-- Attachment #2: Type: text/html, Size: 3938 bytes --]
next reply other threads:[~2007-08-21 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 13:18 Yitzhak Mandelbaum [this message]
2007-08-21 13:34 ` [Caml-list] " Olivier Andrieu
2007-08-21 22:19 ` Yaron Minsky
2007-08-21 13:42 ` Christophe TROESTLER
2007-08-21 13:55 ` Daniel de Rauglaudre
2007-08-21 13:47 ` Virgile Prevosto
2007-08-22 16:32 ` Philippe Wang
2007-08-22 19:24 ` Jeremy Yallop
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=67ECB685-E69A-43CA-867D-30B879DB0510@research.att.com \
--to=yitzhak@research.att.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