From: tab@snarc.org (Vincent Hanquez)
To: rlehy@free.fr
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [OSR] Exceptionless error management, take 2
Date: Fri, 8 Feb 2008 12:56:35 +0100 [thread overview]
Message-ID: <20080208115635.GA2885@snarc.org> (raw)
In-Reply-To: <1202467938.47ac3462d077a@imp.free.fr>
On Fri, Feb 08, 2008 at 11:52:18AM +0100, rlehy@free.fr wrote:
> Could you please expand on this "pollution" and the *practical* problems it
> causes? I can see the risk of my own identifiers clashing with those of a
> library, and that finding documentation when the namespace is flat is harder.
> But none of these seem applicable for polymorphic variants, so I feel like I'm
> missing something.
For example, an `Error returned by module X could be use in a code
expecting an `Error returned by module Y, even though that the `Error
could means something totally different (semanticly). If I use normal
variant, the compiler will prevent me using the same code to match a
X.Error and a Y.Error.
And don't get me wrong, i'm not saying polymorphic variant should never be use,
it has its limited use (when people knows exactly what they are doing),
but usually i prefer keeping this safety net , and like that the
compiler tells me i can't use a Y.Error like a X.Error.
--
Vincent Hanquez
next prev parent reply other threads:[~2008-02-08 11:56 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
2008-02-08 9:53 ` Vincent Hanquez
2008-02-08 10:52 ` rlehy
2008-02-08 11:56 ` Vincent Hanquez [this message]
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=20080208115635.GA2885@snarc.org \
--to=tab@snarc.org \
--cc=caml-list@inria.fr \
--cc=rlehy@free.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