caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: Andrej.Bauer@andrej.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] type unsoundness with constraints and polymorphic variants
Date: Wed, 13 Feb 2008 17:00:18 +0900 (JST)	[thread overview]
Message-ID: <20080213.170018.179955875.garrigue@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <47B17667.2090907@fmf.uni-lj.si>

From: Andrej Bauer <Andrej.Bauer@fmf.uni-lj.si>

> Out of curiosity, is there a document describing the current ocaml 
> typing system, other than the compiler source code?
> 
> More generally, what level of formal specification and verification does 
> ocaml reach? None, well commented code, a fragment of the language is 
> formalized, someone's PhD described the compiler, there is an official 
> document describing the compiler, God gave Xavier the type system on Mt 
> Blanc, or what?

Most of the type system is formalized, but there is no single place to
look at.
Caml Special Light (ocaml minus objects and variants) was mostly based
on Xavier's work, so you can look at his papers for that part (and
more recent extensions of the module system).
Objects were added by Didier Remy and Jerome Vouillon, and Jerome's
thesis is a good source for this.
I worked on labels (with Jun Furuse) and polymorphic variants, so you
may look at my papers for those.
Private types are by Pierre Weis, and I suppose he wrote something on
them too.
And this list is not exhaustive.

Of course all these papers consider each feature independently, and
are not always up to date with the current ocaml implementation, but
if the behaviour does not follow them, there is a high probability
that this is a bug.

Note also that some parts have no published formal specification.
For instance, subtyping coercions, or variance inference. The intended
behaviour is relatively clear though.

Jacques Garrigue


  parent reply	other threads:[~2008-02-13  8:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11 20:03 Stephen Weeks
2008-02-11 20:46 ` [Caml-list] " Markus Mottl
2008-02-12  4:22 ` Jacques Garrigue
2008-02-12 10:35   ` Andrej Bauer
2008-02-12 14:43     ` Luc Maranget
2008-02-13  8:00     ` Jacques Garrigue [this message]
2008-02-13 14:15       ` Christopher L Conway
2008-02-13 14:18         ` Michael Hicks
2008-02-13 14:22           ` David Teller
2008-02-13 14:35           ` Till Varoquaux
2008-02-13 14:52             ` Michael Hicks
2008-02-13 14:53             ` Mattias Engdegård
2008-02-13 15:55               ` Christopher L Conway
2008-02-13 16:53             ` Stefano Zacchiroli

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=20080213.170018.179955875.garrigue@math.nagoya-u.ac.jp \
    --to=garrigue@math.nagoya-u.ac.jp \
    --cc=Andrej.Bauer@andrej.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).