caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: "Mr. Herr" <misterherr@freenet.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Suppress warning from within Ocaml source file
Date: Thu, 12 Nov 2015 13:48:53 +0000	[thread overview]
Message-ID: <9463C955F1814F02BE3D330F5C3E4E17@erratique.ch> (raw)
In-Reply-To: <5644845B.6000801@freenet.de>

Le jeudi, 12 novembre 2015 à 12:21, Mr. Herr a écrit :
> On the other hand:
>  
> it is quite possible that your with-construct is more harmful than useful:
>  
> when extending the record, the compiler will not flag the lines in your code you have
> to check.


That still doesn't answer why this warning exists at all. Of course depending on context you should or should not use `with` according to the kind of type-checking you want when you evolve your code base.

But the purpose of the `with` construct is precisely that you do not have to list all the other fields which is quite natural for functional record updates. Besides the kind of code evolution Michael mentions is also quite natural and thus I don't see why the compiler should complain if you happen to mention all the fields in the with construct.  

Nobody provided me with a good answer to the question: why is this a problem and I should be warned about this ? The only answer I got (cf PR 6179) was "we receive many complaints about warnings so just turn it off".

Daniel





  parent reply	other threads:[~2015-11-12 13:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12  8:49 Soegtrop, Michael
2015-11-12  9:10 ` Gabriel Scherer
2015-11-12  9:33   ` Soegtrop, Michael
2015-11-12  9:44     ` Gabriel Scherer
2015-11-12  9:57       ` Soegtrop, Michael
2015-11-12  9:49   ` Daniel Bünzli
2015-11-12 12:21 ` Mr. Herr
2015-11-12 13:02   ` Soegtrop, Michael
2015-11-12 13:48   ` Daniel Bünzli [this message]
2015-11-12 14:54     ` Soegtrop, Michael
2015-11-12 15:14       ` Daniel Bünzli
2015-11-12 16:37         ` Leo White
2015-11-12 17:26           ` Daniel Bünzli
2015-11-12 18:39             ` Virgile Prevosto
2015-11-12 19:21               ` Gerd Stolpmann
2015-11-12 20:16                 ` Hendrik Boom
2015-11-12 19:34               ` Jeremy Yallop

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=9463C955F1814F02BE3D330F5C3E4E17@erratique.ch \
    --to=daniel.buenzli@erratique.ch \
    --cc=caml-list@inria.fr \
    --cc=misterherr@freenet.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;
as well as URLs for NNTP newsgroup(s).