From: oliver <oliver@first.in-berlin.de>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Articles on using types for enhancing sw-quality?
Date: Mon, 9 Apr 2012 19:43:56 +0200 [thread overview]
Message-ID: <20120409174356.GE28310@siouxsie> (raw)
In-Reply-To: <CAPFanBFtrMSo5WPm8SSRjYhmvzs_zQJMtPsFg-vJcFX9hhutzg@mail.gmail.com>
On Sat, Apr 07, 2012 at 06:45:26PM +0200, Gabriel Scherer wrote:
> In the ML-type-system community, enforcing invariant through typing
> has mostly been discussed, as far as I'm aware, informally, and is
> part of the language communities folklore. There have been
> publications centered on the use of richer features (than the base ML
[...]
Thank you for the many links.
Thats much more than I expected to be there. :-)
Ciao,
Oliver
next prev parent reply other threads:[~2012-04-09 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 15:14 oliver
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 [this message]
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=20120409174356.GE28310@siouxsie \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.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