caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Malcolm Matalka <mmatalka@gmail.com>
To: Mark Shinwell <mshinwell@janestreet.com>
Cc: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>,
	 Yaron Minsky <yminsky@janestreet.com>,
	 ygrek <ygrek@autistici.org>,
	 "caml-list\@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Should -strict-sequence become the default?
Date: Mon, 28 Oct 2013 14:13:20 +0000	[thread overview]
Message-ID: <87ob69scu7.fsf@gmail.com> (raw)
In-Reply-To: <CAM3Ki76f7FuOBQ6+_JR38A+0xBjNJHHZQzHMM9XgaC_PN1WmXQ@mail.gmail.com> (Mark Shinwell's message of "Mon, 28 Oct 2013 09:18:44 -0400")

Sounds like a job for the massive opam computing grid!

Mark Shinwell <mshinwell@janestreet.com> writes:

> On 28 October 2013 09:08, Jacques Garrigue <garrigue@math.nagoya-u.ac.jp> wrote:
>> This said, I personally do not like the statement warning, and I'm not a big
>> fan of
>> -strict-sequence either, as both require changes in APIs.
>
> I'm very much in favour of making -strict-sequence the default.
>
> It doesn't seem to me that, given suitable notice disseminated through this
> mailing list, the change is overly disruptive.  (The fixing of code
> should largely
> be a mechanical process; and the error can be quickly turned off in the event
> of having a particularly problematic source file.)
>
> Mark

      reply	other threads:[~2013-10-28 14:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-27 14:20 Yaron Minsky
2013-10-27 14:43 ` Lukasz Stafiniak
2013-10-27 18:27 ` John Whitington
2013-10-27 18:47   ` Yaron Minsky
2013-10-28 12:42     ` ygrek
2013-10-28 13:00       ` Yaron Minsky
2013-10-28 13:08         ` Jacques Garrigue
2013-10-28 13:18           ` Mark Shinwell
2013-10-28 14:13             ` Malcolm Matalka [this message]

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=87ob69scu7.fsf@gmail.com \
    --to=mmatalka@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=garrigue@math.nagoya-u.ac.jp \
    --cc=mshinwell@janestreet.com \
    --cc=ygrek@autistici.org \
    --cc=yminsky@janestreet.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;
as well as URLs for NNTP newsgroup(s).