From: Leo White <lpw25@cam.ac.uk>
To: Jordan W <jordojw@gmail.com>
Cc: "caml-list\@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Module aliases ideal name-spacing
Date: Mon, 29 Dec 2014 00:14:58 +0000 [thread overview]
Message-ID: <87tx0fjoql.fsf@study.localdomain> (raw)
In-Reply-To: <CAPOA5_6gZ7b8-DRS=YCaDWU2UAbWjvfG=09SOXzPiQSFNmbeng@mail.gmail.com> (Jordan W.'s message of "Sun, 28 Dec 2014 15:25:17 -0800")
> The only remaining remnant of the "prefixed"
> namespace is in myLib.mli/.ml
>
>
> module MyModule = MyLibMyModule
> module Utils = MyLibUtils
>
> It would be nice to eliminate that as well, but I could imagine
> auto-generating these module alias mappings.
It is certainly feasible to have the build system generate these
mappings automatically. For example, I believe that Jane Street's
example build rules for Jenga include support for generating these alias
mappings (examples/js-build-style/jengaroot.ml in the Jenga source
code).
> This
> sounds like a nice workaround the namespace issue, but do you think it would be worth supporting module aliases
> themselves as a form of namespacing at compilation time, so that this intermediate prefixed compilation artifact isn't
> needed?
I'm aware of a few proposals, and I'm sure something more user-friendly
will happen at some point, but the details of these proposals are tricky
and important to get right. For now, the support in 4.02 is at least
sufficient to have a working replacement for `-pack`.
Regards,
Leo
next prev parent reply other threads:[~2014-12-28 23:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 23:04 Jordan W
2014-12-28 18:15 ` Leo White
2014-12-28 20:34 ` Jordo
2014-12-28 21:26 ` Leo White
2014-12-28 23:25 ` Jordan W
2014-12-29 0:14 ` Leo White [this message]
2015-01-07 15:15 ` Goswin von Brederlow
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=87tx0fjoql.fsf@study.localdomain \
--to=lpw25@cam.ac.uk \
--cc=caml-list@inria.fr \
--cc=jordojw@gmail.com \
/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