From: oliver <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: [Caml-list] Articles on using types for enhancing sw-quality?
Date: Sat, 7 Apr 2012 17:14:52 +0200 [thread overview]
Message-ID: <20120407151452.GA12887@siouxsie> (raw)
Hello,
do you know of articles (or books?) that describe
the usage of types for enhancing software quality
by coding the software invariants as types?
(And if possible, for example enforce certain operations
on such values, maybe also encoded as types?)
I remember an interesting talk from Yaron Minsky
on that topic.
But this rather was an explanation on
why OCaml and other strongly typed languages are
very useful to ensure software integrity by the
type system. There were examples, but not completely
going too much into depth there.
I would like to explore this more thoroughly and look
for articles / books (or other videos), that explain
the design technique in more depth.
So, if you know of something regarding this topic,
please let me know.
Ciao,
Oliver
next reply other threads:[~2012-04-07 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 15:14 oliver [this message]
2012-04-07 16:45 ` Gabriel Scherer
2012-04-09 5:37 ` Cedric Cellier
2012-04-09 6:51 ` Gabriel Kerneis
2012-04-09 7:11 ` Gabriel Scherer
2012-04-09 17:43 ` oliver
2012-04-08 9:46 ` Daniel Bünzli
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=20120407151452.GA12887@siouxsie \
--to=oliver@first.in-berlin.de \
--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