From: ygrek <ygrek@autistici.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Should -strict-sequence become the default?
Date: Mon, 28 Oct 2013 14:42:15 +0200 [thread overview]
Message-ID: <20131028144215.3e546e24@kiwi.local.tld> (raw)
In-Reply-To: <CACLX4jQrQugpBcJjy9-LZW=kF3XkkU69Tr-5AwVa0cOv4oCtWw@mail.gmail.com>
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.
--
next prev parent reply other threads:[~2013-10-28 12:42 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 [this message]
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
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=20131028144215.3e546e24@kiwi.local.tld \
--to=ygrek@autistici.org \
--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;
as well as URLs for NNTP newsgroup(s).