From: Christopher Quinn <cq@htec.demon.co.uk>
To: Damien Doligez <damien.doligez@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] assertions and branch prediction
Date: Mon, 18 Feb 2002 13:41:01 +0000 [thread overview]
Message-ID: <3C71046D.7090409@htec.demon.co.uk> (raw)
In-Reply-To: <200202171347.OAA0000013262@beaune.inria.fr>
May I ask how
| _ -> assert (not true); ()
is different from
| _ -> assert false; ()
???
Thanks,
chris
Damien Doligez wrote:
>>From: james woodyatt <jhw@wetware.com>
>>
>
>> match p with
>> | A -> ...; ()
>> | B -> ...; ()
>> | _ -> assert false
>>
>>Then I hit upon the idea of rewriting it this way:
>>
>> assert (p = A || p = B);
>> match p with
>> | A -> ...; ()
>> | B -> ...; ()
>> | C -> ()
>>
>>My thinking was that I would rather pay up front with a more expensive
>>assertion, one that can be stripped out later with the -noassert option,
>>rather than pay at deployment with code (for raising the Assert_failure
>>exception) that I've eventually proven will not be executed.
>>
>
>You can have the best of both worlds by writing it like this:
>
> match p with
> | A -> ...; ()
> | B -> ...; ()
> | _ -> assert (not true); ()
>
>
>As for "assert false" with -noassert, you're not really supposed to
>catch the Assert_failure exception (unless you really know what
>you're doing), so it should result in the immediate termination of
>your program anyway.
>
>-- Damien
>-------------------
>Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
>To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
>
--
rgrds,
Chris Quinn
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2002-02-18 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-17 13:47 Damien Doligez
2002-02-18 13:41 ` Christopher Quinn [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-18 17:06 Damien Doligez
2002-02-15 17:01 james woodyatt
2002-02-18 14:00 ` Xavier Leroy
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=3C71046D.7090409@htec.demon.co.uk \
--to=cq@htec.demon.co.uk \
--cc=caml-list@inria.fr \
--cc=damien.doligez@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