From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Preferred use of Invalid_argument and Failure
Date: Wed, 24 Oct 2007 15:44:01 +0100 [thread overview]
Message-ID: <200710241544.01703.jon@ffconsultancy.com> (raw)
In-Reply-To: <891bd3390710240615j7916d8adua64ef1104f3444a8@mail.gmail.com>
On Wednesday 24 October 2007 14:15:36 Yaron Minsky wrote:
> As in:
>
> map_of_alist : ('a * 'b) list -> [ `Repeated_key of 'a | `Succ of ('a,'b)
> Map.t ]
>
> The return value is both explicit and a polymorphic variant.
We also use that pattern. I'll document it somewhere...
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?e
next prev parent reply other threads:[~2007-10-24 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 6:45 Michaël Le Barbier
2007-10-24 7:06 ` [Caml-list] " Alain Frisch
2007-10-24 8:06 ` Xavier Leroy
2007-10-24 11:05 ` Yaron Minsky
2007-10-24 11:30 ` Joel Reymont
2007-10-24 13:15 ` Yaron Minsky
2007-10-24 13:22 ` Daniel Bünzli
2007-10-24 14:45 ` Jon Harrop
2007-10-24 15:10 ` Richard Jones
2007-10-24 14:44 ` Jon Harrop [this message]
2007-10-25 7:07 ` Michaël Le Barbier
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=200710241544.01703.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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).