From: "vrotaru.md@gmail.com" <vrotaru.md@gmail.com>
To: "Petter A. Urkedal" <paurkedal@gmail.com>,
Hendrik Boom <hendrik@topoi.pooq.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Warnings opening modules (was: why is building ocaml hard?)
Date: Sat, 16 Jul 2016 09:58:39 +0000 [thread overview]
Message-ID: <CAJgjwehskByKQXr2Qv6v7kp00rhxExLEhBbsBoUgTqQcB-gm6w@mail.gmail.com> (raw)
In-Reply-To: <CALa9pHScpu3Dt6nirsjNiBFc=H_qxzxXFGjWRtNvuS6CWMJ_xg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]
About that missing type constructors problem. Seems doable:
module A = struct
module T = struct
type t1 = ...
type t2 = ...
end
include T
let foo _ = ...
let bar : t2 -> t1 = ...
end
module B = struct
include A.T
let foo, bar = A.( foo, bar )
end
Obviously, not for already existing code.
În sâm., 16 iul. 2016 la 10:41, Petter A. Urkedal <paurkedal@gmail.com> a
scris:
> On 15 July 2016 at 18:13, Hendrik Boom <hendrik@topoi.pooq.com> wrote:
> > And that's a real problem -- that fact that openning a module can fill
> > the namespace with lots of stray identifiers, which the user does not
> > control.
>
> Apart from the selective opens discussed, it would be good to tell
> apart which modules are meant to be open and which are intrusive
> without looking through them. Most importantly the writer of the
> library should be clear about it from the start when designing a
> module, then the names will be consistent with the choice, and users
> should be able to decide without evaluating the whole interface.
>
> A warning when opening an invasive module in a global scope could
> help, as well. One could maybe decide a module to be invasive from a
> few heuristics with fall-back to a declaration:
>
> - A module interface defining a single-letter identifier, most
> importantly a type "t" or a signature "S", is invasive.
> - A module interface overriding any operator (or identifier?) defined
> in Pervasives is invasive.
> - A module interface declaring itself `[@@@ocaml.invasive]` is invasive.
>
> Conversely the user may silence the warning with `open M
> [@@ocaml.invasive]`.
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 2827 bytes --]
next prev parent reply other threads:[~2016-07-16 9:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 11:57 David Allsopp
2016-07-10 19:45 ` Gerd Stolpmann
2016-07-13 12:08 ` David Allsopp
2016-07-13 12:20 ` Gerd Stolpmann
2016-07-13 12:30 ` David Allsopp
2016-07-14 9:03 ` Goswin von Brederlow
2016-07-15 9:52 ` David Allsopp
2016-07-15 16:13 ` Hendrik Boom
2016-07-15 16:57 ` Yotam Barnoy
2016-07-15 18:09 ` Jeremy Yallop
2016-07-15 18:26 ` Hendrik Boom
2016-07-15 18:58 ` Yotam Barnoy
2016-07-15 19:26 ` Hezekiah M. Carty
2016-07-15 19:42 ` Yotam Barnoy
2016-07-15 19:52 ` Jeremy Yallop
2016-07-15 20:25 ` Yotam Barnoy
2016-07-15 18:50 ` Alain Frisch
2016-07-15 19:44 ` Hendrik Boom
2016-07-15 17:04 ` Gerd Stolpmann
2016-07-20 7:49 ` Louis Gesbert
2016-07-16 7:40 ` Petter A. Urkedal
2016-07-16 9:58 ` vrotaru.md [this message]
2016-07-19 16:37 ` Yotam Barnoy
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=CAJgjwehskByKQXr2Qv6v7kp00rhxExLEhBbsBoUgTqQcB-gm6w@mail.gmail.com \
--to=vrotaru.md@gmail.com \
--cc=caml-list@inria.fr \
--cc=hendrik@topoi.pooq.com \
--cc=paurkedal@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