From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Nils Becker <nils.becker@bioquant.uni-heidelberg.de>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] destructive local opens
Date: Mon, 17 Aug 2015 17:18:13 +0200 [thread overview]
Message-ID: <CAPFanBFDeZJJm1kmuAfAfyks9H103JYZOYz=r__Xys3KaLwVFw@mail.gmail.com> (raw)
In-Reply-To: <55D1F989.1040804@bioquant.uni-heidelberg.de>
Note that forcing you to use "let open! M" instead of M.!(...) is
already a way to make you pay.
On Mon, Aug 17, 2015 at 5:11 PM, Nils Becker
<nils.becker@bioquant.uni-heidelberg.de> wrote:
> On 17/08/15 16:26, Gabriel Scherer wrote:
>> both (let open!)
>> and M.!(...) are dangerous constructions that should be avoided
>> whenever possible, and that we could and should drastically reduce the
>> number of situations where the user is encouraged to use them.
>
> This may have been brought up before, but one way to discourage would be
> to make it very verbose. One would require both (let open!) or M.!() at
> the shadowing site and an extra annotation for each identifier or
> operator in M's signature that is supposed to shadow. The signature
> would then have to carry that information around.
>
> Then M.() would never shadow, M.!() indicates possibility of shadowing
> and by looking at the type of M one can see which of M's values are
> actually shadowing? A tool like merlin could then even annotate this
> graphically.
>
> but this may be too drastic a change...
>
> n.
>
> --
> 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
next prev parent reply other threads:[~2015-08-17 15:18 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 10:17 Nils Becker
2015-08-17 14:26 ` Gabriel Scherer
2015-08-17 15:11 ` Nils Becker
2015-08-17 15:17 ` Drup
2015-08-17 15:18 ` Gabriel Scherer [this message]
2015-08-17 18:31 ` Hendrik Boom
-- strict thread matches above, loose matches on Subject: below --
2015-08-03 13:39 Nils Becker
2015-08-03 13:43 ` Thomas Refis
2015-08-03 13:45 ` Daniel Bünzli
2015-08-03 13:47 ` Daniel Bünzli
[not found] ` <55BF75F6.1040006@bioquant.uni-heidelberg.de>
2015-08-03 14:24 ` Daniel Bünzli
2015-08-03 14:37 ` Gabriel Scherer
2015-08-03 14:43 ` Daniel Bünzli
2015-08-03 15:10 ` octachron
2015-08-03 15:22 ` Daniel Bünzli
2015-08-03 16:13 ` octachron
2015-08-03 16:51 ` Daniel Bünzli
2015-08-03 17:18 ` Hendrik Boom
2015-08-03 17:59 ` octachron
2015-08-04 6:51 ` Petter Urkedal
2015-08-04 9:33 ` Goswin von Brederlow
2015-08-05 6:40 ` Petter A. Urkedal
2015-08-05 10:16 ` David Allsopp
2015-08-06 9:35 ` Goswin von Brederlow
2015-08-04 13:50 ` Hendrik Boom
2015-08-04 9:26 ` Goswin von Brederlow
2015-08-04 9:38 ` Daniel Bünzli
2015-08-04 12:26 ` vrotaru.md
2015-08-04 13:12 ` David Allsopp
2015-08-04 13:17 ` Jeremy Yallop
2015-08-04 13:54 ` vrotaru.md
2015-08-04 15:25 ` Drup
2015-08-04 22:22 ` vrotaru.md
2015-08-04 22:55 ` Hendrik Boom
2015-08-05 4:52 ` Gabriel Scherer
2015-08-04 13:14 ` Ivan Gotovchits
2015-08-14 10:55 ` Goswin von Brederlow
2015-08-14 11:28 ` Drup
2015-08-18 11:11 ` Goswin von Brederlow
2015-08-18 12:52 ` David Allsopp
2015-08-18 13:00 ` Gabriel Scherer
2015-08-18 22:26 ` Anthony Tavener
2015-08-19 13:55 ` Oleg
2015-08-19 14:13 ` John Whitington
2015-08-19 15:47 ` Hendrik Boom
2015-08-19 15:52 ` Hendrik Boom
2015-08-19 18:09 ` Anthony Tavener
2015-08-19 15:55 ` Simon Cruanes
2015-08-19 16:42 ` Arthur Wendling
2015-08-19 21:15 ` octachron
2015-08-20 8:06 ` Romain Bardou
2015-08-20 17:03 ` Yotam Barnoy
2015-08-20 19:19 ` Erkki Seppala
2015-08-06 9:23 ` Goswin von Brederlow
2015-08-06 9:21 ` Goswin von Brederlow
2015-08-06 10:19 ` Daniel Bünzli
2015-08-06 13:36 ` Hendrik Boom
2015-08-14 10:57 ` 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='CAPFanBFDeZJJm1kmuAfAfyks9H103JYZOYz=r__Xys3KaLwVFw@mail.gmail.com' \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=nils.becker@bioquant.uni-heidelberg.de \
/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