caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yaron Minsky <yminsky@janestreet.com>
To: ygrek <ygrek@autistici.org>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Should -strict-sequence become the default?
Date: Mon, 28 Oct 2013 09:00:34 -0400	[thread overview]
Message-ID: <CACLX4jRoQAE5SkRr2ekuMUWRP9ZXiEF7taZYwPWmep-ZUb6h=w@mail.gmail.com> (raw)
In-Reply-To: <20131028144215.3e546e24@kiwi.local.tld>

Interesting.  Anyone know if the disabling of 21 with strict-sequence
is a fundamental issue, or just an accident?  It seems best to have
both available at once.

y

On Mon, Oct 28, 2013 at 8:42 AM, ygrek <ygrek@autistici.org> wrote:
> Hello,
>
> I have one problem with this option. Basically - it disables warning 21. Consider:
>
> $ ocaml
>
> # let f () = exit 0; 1;;
> Characters 11-17:
>   let f () = exit 0; 1;;
>              ^^^^^^
> Warning 21: this statement never returns (or has an unsound type.)
> val f : unit -> int = <fun>
>
> $ ocaml -strict-sequence
>
> # let f () = exit 0; 1;;
> val f : unit -> int = <fun>
>
> So I choose to disable this option and strictly require `let () =` when calling callbacks.
>
> --
>
> --
> 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

  reply	other threads:[~2013-10-28 13:00 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 [this message]
2013-10-28 13:08         ` Jacques Garrigue
2013-10-28 13:18           ` Mark Shinwell
2013-10-28 14:13             ` Malcolm Matalka

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='CACLX4jRoQAE5SkRr2ekuMUWRP9ZXiEF7taZYwPWmep-ZUb6h=w@mail.gmail.com' \
    --to=yminsky@janestreet.com \
    --cc=caml-list@inria.fr \
    --cc=ygrek@autistici.org \
    /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).