From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: SP <sp@orbitalfox.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] What if exn was not an open type?
Date: Tue, 24 Oct 2017 13:16:40 +0200 [thread overview]
Message-ID: <CAPFanBEuzzOPVcCtWRT5=4EazqxDRrp2FZkWRH6p+HR-UTDz5w@mail.gmail.com> (raw)
In-Reply-To: <bbb6a9c7-5d5f-6653-4039-022ad3a2bed0@orbitalfox.com>
[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]
Participants to this discussion may be interested in the article "Catch me
if you can", by David Teller, Arnaud Spiwack and Till Varoquaux, 2008:
https://hal.inria.fr/inria-00432575
This is the year 2008 and ML-style exceptions are everywhere. Most modern
> languages, whether academic or industrial, feature some variant of this
> mechanism. Languages such as Java even feature static coverage-checking for
> such exceptions, something not available for ML languages, at least not
> without resorting to external tools. In this document, we demonstrate a
> design principle and a tiny library for managing errors in a functional
> manner, with static coverage-checking, automatically-inferred, structurally
> typed and hierarchical exceptional cases, with a reasonable run-time
> penalty. Our work is based on OCaml and features monads, polymorphic
> variants, compile-time code rewriting and trace elements of black magic.
On Tue, Oct 24, 2017 at 1:11 PM, SP <sp@orbitalfox.com> wrote:
> On 22/10/2017 13:39, Malcolm Matalka wrote:
> > I'm one of those people that uses result everywhere + result monad where
> > the error case is a polymorphic variant. This lets me get the value of
> > an open type with power of an exhaustive pattern match check. No
> > strings needed.
>
> Nice!
>
> --
> SP
>
> --
> 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
>
[-- Attachment #2: Type: text/html, Size: 2506 bytes --]
next prev parent reply other threads:[~2017-10-24 11:17 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 9:56 Malcolm Matalka
2017-10-20 10:55 ` David Allsopp
2017-10-20 11:21 ` Ivan Gotovchits
2017-10-20 11:38 ` Simon Cruanes
2017-10-20 16:54 ` Malcolm Matalka
2017-10-20 19:47 ` Simon Cruanes
2017-10-21 21:15 ` Malcolm Matalka
2017-10-24 13:30 ` Richard W.M. Jones
2017-10-24 19:02 ` Petter A. Urkedal
2017-11-04 18:44 ` Richard W.M. Jones
2017-11-04 18:48 ` SP
2017-11-04 18:53 ` Richard W.M. Jones
2017-11-04 19:03 ` SP
2017-11-04 19:01 ` Max Mouratov
2017-11-04 19:16 ` octachron
2017-11-05 17:41 ` Richard W.M. Jones
2017-11-05 18:39 ` Yaron Minsky
2017-11-05 20:49 ` Gabriel Scherer
2017-11-05 21:48 ` Yaron Minsky
2017-11-05 21:53 ` Petter A. Urkedal
2017-11-05 18:02 ` Petter A. Urkedal
2017-11-05 18:24 ` Richard W.M. Jones
2017-11-05 18:55 ` Petter A. Urkedal
[not found] ` <CALa9pHQ-nhWf4T0U5gDiKTduPiEeXSZPQ=DY6N1YNbCXqRohPQ@mail.gmail.com>
2017-10-25 8:35 ` Richard W.M. Jones
2017-10-25 9:12 ` Philippe Veber
2017-10-25 14:52 ` Richard W.M. Jones
2017-10-25 16:37 ` Ivan Gotovchits
2017-10-25 17:47 ` SP
2017-10-26 8:06 ` Malcolm Matalka
2017-10-26 8:11 ` Xavier Leroy
2017-10-25 13:36 ` Ivan Gotovchits
2017-10-26 7:31 ` Petter A. Urkedal
2017-10-27 13:58 ` Oleg
2017-10-27 14:24 ` Philippe Veber
2017-10-27 14:49 ` Leo White
2017-11-01 7:16 ` Oleg
2017-11-04 17:52 ` Philippe Veber
2017-10-20 17:07 ` Malcolm Matalka
2017-10-21 21:28 ` Nathan Moreau
2017-10-22 12:39 ` Malcolm Matalka
2017-10-22 13:08 ` Nathan Moreau
2017-10-24 11:11 ` SP
2017-10-24 11:16 ` Gabriel Scherer [this message]
2017-10-25 11:30 ` Malcolm Matalka
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='CAPFanBEuzzOPVcCtWRT5=4EazqxDRrp2FZkWRH6p+HR-UTDz5w@mail.gmail.com' \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=sp@orbitalfox.com \
/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