From: Edgar Friendly <thelema314@gmail.com>
To: David Teller <David.Teller@univ-orleans.fr>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] "Warning U: this match case is unused." -- Yes, I know
Date: Wed, 27 Feb 2008 16:09:00 -0600 [thread overview]
Message-ID: <47C5DF7C.4010107@gmail.com> (raw)
In-Reply-To: <1204147958.7005.17.camel@Blefuscu>
David Teller wrote:
> Dear list,
>
> I'm currently working on a little Camlp4 extension which has to often
> generate pattern-matching clauses depending on user code -- and deal
> with match failures accordingly.
>
> Now, I guess
>
> 1. I can wrap the user's pattern-matching inside a try...with, catch any
> Match_failure and deal with it.
This seems hackish.
> 2. I can add a catch-all clause " _ -> deal_with_error ". While the
> semantics of this rewriting are exactly what I need, the compiler tends
> to print "Warning U: this match case is unused" whenever the user has
> already taken care of all cases.
It may seem that you've taken care of all cases, but keep in mind that
the compiler looks at a match case containing a 'when' clause and
assumes that clause can cause the match to fail, independent of all
other terms.
i.e. if you write:
match 123 with
| x when x mod 2 = 1 -> "Odd"
| x when x mod 2 = 0 -> "Even"
The compiler can't see that you've covered all cases. Even the
following generates a warning:
match 123 with x when true -> "TRUE" | x when false -> "FALSE"
The way I write this style of matching goes like this:
match 123 with
| x when x mod 2 = 1 -> "Odd"
| x (* x mod 2 = 0 *) -> "Even"
Can you structure your matches this way?
E.
next prev parent reply other threads:[~2008-02-27 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 21:32 David Teller
2008-02-27 21:48 ` [Caml-list] " Till Varoquaux
2008-02-27 21:56 ` David Teller
2008-02-27 22:09 ` Edgar Friendly [this message]
2008-02-27 22:21 ` David Teller
2008-02-27 22:30 ` Edgar Friendly
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=47C5DF7C.4010107@gmail.com \
--to=thelema314@gmail.com \
--cc=David.Teller@univ-orleans.fr \
--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