From: Jean-Christophe Filliatre <Jean-Christophe.Filliatre@lri.fr>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] 'should have type unit' warning in 'let _ =' ?
Date: Wed, 16 Jul 2003 09:11:17 +0200 [thread overview]
Message-ID: <16148.64149.159637.17355@gargle.gargle.HOWL> (raw)
In-Reply-To: <20030716091051K.garrigue@kurims.kyoto-u.ac.jp>
Jacques Garrigue writes:
> A middle ground would be to only warn when the wild pattern matches a
> function type
That would be great!
Could it be done before 3.07 is released? :-)
--
Jean-Christophe
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2003-07-16 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 0:29 henridf
2003-07-15 1:04 ` Jacques Garrigue
2003-07-15 11:36 ` Richard Jones
2003-07-16 0:10 ` Jacques Garrigue
2003-07-16 7:11 ` Jean-Christophe Filliatre [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=16148.64149.159637.17355@gargle.gargle.HOWL \
--to=jean-christophe.filliatre@lri.fr \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
/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