From: Andrej Bauer <Andrej.Bauer@fmf.uni-lj.si>
To: "Michaël Le Barbier" <michael.le_barbier@laposte.net>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Strategy to avoid name collision in signatures
Date: Sat, 03 Nov 2007 23:47:24 +0100 [thread overview]
Message-ID: <472CFA7C.60901@fmf.uni-lj.si> (raw)
In-Reply-To: <86tzo3nf8f.fsf@Llea.celt.neu>
Michaël Le Barbier wrote:
> include OrderedType.Make(struct ... end)
> include FunnyType.Make(struct ... end)
Can you give a convincing example that would prevent you from separating
these two with tsubmodules, i.e.,
module AsOrd = OrderedType.Make(struct ... end)
module AsFunny = FunnyType.Make(struct ... end)
If you really want to "blend" together OrderedType and FunnyType in the
same module, then they must be meaningfully related. What example do you
have in mind?
Andrej
next prev parent reply other threads:[~2007-11-03 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 22:20 Michaël Le Barbier
2007-11-03 22:47 ` Andrej Bauer [this message]
2007-11-04 6:15 ` [Caml-list] " Michaël Le Barbier
2007-11-04 0:01 ` Julien Moutinho
2007-11-04 7:34 ` Michaël Le Barbier
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=472CFA7C.60901@fmf.uni-lj.si \
--to=andrej.bauer@fmf.uni-lj.si \
--cc=Andrej.Bauer@andrej.com \
--cc=caml-list@yquem.inria.fr \
--cc=michael.le_barbier@laposte.net \
/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