From: Markus Elfring <Markus.Elfring@web.de>
To: Oliver Bandel <oliver@first.in-berlin.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Error handling in FPLs (Re: Detecting missed checks for error indications in ML code)
Date: Sat, 30 Jan 2021 12:51:00 +0100 [thread overview]
Message-ID: <ecd4495d-9b5c-ab85-801f-e044d031a977@web.de> (raw)
In-Reply-To: <20210129211425.gqto6k3qz6g7kvkp@first.in-berlin.de>
> What do you think about this here:
>
> Railway oriented programming: Error handling in functional languages by Scott Wlaschin
> https://vimeo.com/113707214
>
> And about the "bind" here:
> https://dev.realworldocaml.org/error-handling.html
These links refer to helpful information.
> Does that address what you are looking for?
I am trying to increase the software development attention also for cross-cutting concerns.
Error-aware return types support the possibility to provide some data as a return value.
Under which circumstances would you actually check or overlook them?
Exception objects can not be ignored (by default) instead.
Regards,
Markus
prev parent reply other threads:[~2021-01-30 11:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 11:42 [Caml-list] Detecting missed checks for error indications in ML code Markus Elfring
2021-01-24 14:08 ` Hendrik Boom
2021-01-24 15:28 ` Markus Elfring
2021-01-24 14:34 ` Oliver Bandel
2021-01-24 15:52 ` Markus Elfring
2021-01-24 16:07 ` Oliver Bandel
2021-01-24 16:21 ` Markus Elfring
2021-01-25 3:59 ` Yawar Amin
2021-01-25 18:55 ` Markus Elfring
2021-01-24 16:18 ` Oliver Bandel
2021-01-24 16:50 ` Markus Elfring
2021-01-29 21:14 ` [Caml-list] Error handling in FPLs (Re: Detecting missed checks for error indications in ML code) Oliver Bandel
2021-01-30 11:51 ` Markus Elfring [this message]
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=ecd4495d-9b5c-ab85-801f-e044d031a977@web.de \
--to=markus.elfring@web.de \
--cc=caml-list@inria.fr \
--cc=oliver@first.in-berlin.de \
/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).