caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>,
	"Mr. Herr" <misterherr@freenet.de>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] Suppress warning from within Ocaml source file
Date: Thu, 12 Nov 2015 14:54:53 +0000	[thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A172CE3F675@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <9463C955F1814F02BE3D330F5C3E4E17@erratique.ch>

Dear Daniel,

> 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.

as far as I understood the point is that it is questionable if using with at all in such situations is a good idea. If with is not used and new fields are added, the compiler will warn about missing fields. Depending on the situation this might be more helpful, because even if you have a with, it might be that you still have to add new fields later, which is hidden by the with.

So one can argue that the point of this warning is that if a with already does provide some fields "automatically" it is useful, but if the with doesn't really do anything you might be better of without the with and the warnings you get when you extend the record.

I would say both views are valid, and it is a matter of taste.

Best regards,

Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

  reply	other threads:[~2015-11-12 14:54 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
2015-11-12 14:54     ` Soegtrop, Michael [this message]
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=0F7D3B1B3C4B894D824F5B822E3E5A172CE3F675@IRSMSX102.ger.corp.intel.com \
    --to=michael.soegtrop@intel.com \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    --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).