From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Alain Frisch <alain.frisch@lexifi.com>
Cc: Matej Kosik <5764c029b688c1c0d24a2e97cd764f@gmail.com>,
caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] exception Foo = Bar.Baz
Date: Mon, 25 Jul 2016 16:05:50 -0400 [thread overview]
Message-ID: <CAPFanBGdwrcDOasV5y5fJEqE1jdxAeze2=NkkToZxpuow9C-2w@mail.gmail.com> (raw)
In-Reply-To: <07e4f1d2-f61f-4047-b1a0-7339b78825e3@lexifi.com>
I think it would be nice for users that only read .mli files to know
equalities between exceptions, for example if they want to reason on
exhaustiveness of exception handling clauses with respect to a given
(informal) exception specification.
On Mon, Jul 25, 2016 at 4:02 PM, Alain Frisch <alain.frisch@lexifi.com> wrote:
> On 25/07/2016 16:34, Matej Kosik wrote:
>>
>> That means that, at present, one can put something like:
>>
>> exception Foo = Bar.Baz
>>
>> inside a _module structure_.
>>
>> I am currently wondering why we are not allowed (also) to put this into a
>> _module signature_ ?
>> Is this a deliberate decision (why?) or merely an omission?
>
>
> What would be the use of putting that in a module signature instead of just
> "exception Foo"? (This could perhaps allow the compiler to report more
> pattern as being useless, but this is of limit benefit.)
>
> -- Alain
>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2016-07-25 20:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 14:34 Matej Kosik
2016-07-25 20:02 ` Alain Frisch
2016-07-25 20:05 ` Gabriel Scherer [this message]
2016-07-26 9:36 ` Leo White
2016-07-26 12:37 ` Gabriel Scherer
2016-07-26 16:27 ` Alain Frisch
2016-07-26 16:32 ` Gabriel Scherer
2016-07-27 8:07 ` Alain Frisch
2016-07-27 8:27 ` Gabriel Scherer
2016-07-27 8:38 ` Alain Frisch
2016-07-27 8:19 ` Leo White
2016-07-26 9:02 ` Matej Kosik
2016-07-26 12:13 ` Gerd Stolpmann
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='CAPFanBGdwrcDOasV5y5fJEqE1jdxAeze2=NkkToZxpuow9C-2w@mail.gmail.com' \
--to=gabriel.scherer@gmail.com \
--cc=5764c029b688c1c0d24a2e97cd764f@gmail.com \
--cc=alain.frisch@lexifi.com \
--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;
as well as URLs for NNTP newsgroup(s).