From: Hendrik Boom <hendrik@topoi.pooq.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] destructive local opens
Date: Mon, 3 Aug 2015 13:18:38 -0400 [thread overview]
Message-ID: <20150803171838.GB28796@topoi.pooq.com> (raw)
In-Reply-To: <2C582E7B7CD34029998882AA66299107@erratique.ch>
On Mon, Aug 03, 2015 at 05:51:24PM +0100, Daniel Bünzli wrote:
> Le lundi, 3 août 2015 à 17:13, octachron a écrit :
> > > The benefit is that I can understand what is happening by only looking at the expression I'm reading. With your proposal I also need to go read the library source to understand what is happening.
> >
> > I think that it is partially true. For instance, with a vector library,
> > "*" is always quite ambiguous: Is this the original scalar
> > multiplication? The vector product? The tensor product? The external
> > product? The Clifford algebra product? These ambiguities already needs
> > to be resolved in the documentation;
>
>
> Note that what you raise here is a different issue it's not about
> knowing *if* the operator is the one from M.() or the one in scope,
> but which one is implemented. Very often this can be disambiguised by
> the surrounding context and, if your operator are few (which they
> should be), is learnable in practice.
>
> With the operator warning splitting rule. The inferences are very
> simple:
>
> 1. Given a M.( * ) without warning the * may be the one of M or the
> one in scope. Ambiguous, can't be resolved locally.
>
> 2. Given a M.( id ) without warning, if [id] is in scope I *know*
> this [id] is being used. If it's not I know M.id is being used. No
> ambiguity, can be resolved locally.
>
> If you allow each identifier in a module to sport an @shadow
> annotation you lose 2. which I find a very valuable property.
> Without it, given that identifiers are much more widespread than
> operators, we get a much more ambiguous language.
It is important that simple deductions enable the reader to understand
what a program means.
With a statically checking compiler (what other kind is really useful)
I rely on the absence of error messages when I perform these simple
deductions.
Therefore I prefer to either have an explicit error message or an
explicit disambiguation.
-- hendrik
next prev parent reply other threads:[~2015-08-03 17:18 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2015-08-03 17:59 ` octachron
2015-08-06 13:23 ` RE : " moreno pedro
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
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
2015-08-17 18:31 ` Hendrik Boom
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=20150803171838.GB28796@topoi.pooq.com \
--to=hendrik@topoi.pooq.com \
--cc=caml-list@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