From: David Teller <David.Teller@univ-orleans.fr>
To: Olivier Andrieu <oandrieu@nerim.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [OSR] Exceptionless error management, take 2
Date: Thu, 07 Feb 2008 17:23:40 +0100 [thread overview]
Message-ID: <1202401420.6084.49.camel@Blefuscu> (raw)
In-Reply-To: <95513600802070806p38d1cf6fxa5726477facb901b@mail.gmail.com>
You're correct: if I do specify manually in the interface that the type
of parse_int is
string -> (int, [`Syntax | `Overflow]) may_fail
rather than the inferred
string -> (int, [> `Syntax | `Overflow) may_fail
I will be safe. I hadn't paid attention to that. I'll rectify my
recommendation.
I still believe that's one pitfall too many but yes, the pitfall is much
smaller than what I had in mind.
Cheers,
David
On Thu, 2008-02-07 at 17:06 +0100, Olivier Andrieu wrote:
> Err no, it's not, you'll get a type error since the variant is closed
> in the signature of parse_int:
>
> This pattern matches values of type (int, [> `IncorrectSyntax ])
> may_fail
> but is here used to match values of type
> (int, [ `Overflow | `Syntax ]) may_fail
> The second variant type does not allow tag(s) `IncorrectSyntax
>
--
David Teller
Security of Distributed Systems
http://www.univ-orleans.fr/lifo/Members/David.Teller
Angry researcher: French Universities need reforms, but the LRU act
brings liquidations.
next prev parent reply other threads:[~2008-02-07 16:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 15:01 David Teller
2008-02-07 15:09 ` [Caml-list] " Vincent Hanquez
2008-02-07 16:40 ` David Teller
2008-02-07 15:17 ` Jacques Garrigue
2008-02-07 15:22 ` Jon Harrop
2008-02-08 9:54 ` Vincent Hanquez
2008-02-07 15:52 ` David Teller
2008-02-07 16:06 ` Olivier Andrieu
2008-02-07 16:23 ` David Teller [this message]
2008-02-08 9:53 ` Vincent Hanquez
2008-02-08 10:52 ` rlehy
2008-02-08 11:56 ` Vincent Hanquez
2008-02-08 12:40 ` Bünzli Daniel
2008-02-08 15:39 ` David Teller
2008-02-08 17:06 ` Eric Cooper
2008-02-08 20:02 ` David Teller
2008-02-08 19:29 ` Bünzli Daniel
2008-02-08 21:13 ` David Teller
2008-02-10 12:35 ` Vincent Hanquez
2008-02-08 19:07 ` Jon Harrop
2008-02-10 11:58 ` Vincent Hanquez
2008-02-10 16:51 ` Matthew William Cox
2008-02-07 15:33 ` Jon Harrop
2008-02-07 16:25 ` David Teller
2008-02-07 23:10 ` David Teller
2008-02-10 18:47 ` Yaron Minsky
2008-02-10 22:05 ` David Teller
2008-02-11 2:16 ` Yaron Minsky
2008-02-11 8:45 ` David Teller
2008-02-11 12:12 ` Yaron Minsky
2008-02-11 12:53 ` David Teller
2008-02-11 23:09 ` Yaron Minsky
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=1202401420.6084.49.camel@Blefuscu \
--to=david.teller@univ-orleans.fr \
--cc=caml-list@inria.fr \
--cc=oandrieu@nerim.net \
/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