caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jeremy Yallop <yallop@gmail.com>
To: Chet Murthy <murthy.chet@gmail.com>
Cc: Oleg <oleg@okmij.org>, Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Are record types generative?
Date: Tue, 23 Jan 2018 22:06:55 +0000	[thread overview]
Message-ID: <CAAxsn=E5fyfPrtvr6StMRoebAuwOOR7GoBXhz=hbAnpdQG+_Zw@mail.gmail.com> (raw)
In-Reply-To: <CA++P_gcLGJA5whF41KiP++SHgabGvue4bJd1gPf233tGP6NfWQ@mail.gmail.com>

On 23 January 2018 at 21:36, Chet Murthy <murthy.chet@gmail.com> wrote:
> Heh. I was careful to say "caml", not "ocaml".   I'm aware that polymorphic
> variants, objects, and (heh, I forgot) labels all violate the rule. And of
> course, modules do.
>
> Like I said: *caml* has this property.  Certainly caml-light, circa 1993
> did, IIRC.

I think people usually consider OCaml an implementation of Caml.
(See, e.g. the documentation at http://caml.inria.fr/)

Of course, you're quite right that most of these programs weren't
valid in caml light.  But even (later versions of) caml light had
format strings with string syntax, so it was possible to write
programs that were rejected without annotations and accepted with
annotations.

In any case, whether annotations can be erased without affecting type
correctness is an interesting property to consider.  Here's a closely
related property that's much harder to break: does adding annotations
leave the run-time behaviour of a program unchanged?  There are far
fewer programs that violate that property, I think.

  reply	other threads:[~2018-01-23 22:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 14:54 Oleg
2018-01-23 16:05 ` Jeremy Yallop
2018-01-23 17:39   ` Chet Murthy
2018-01-23 20:35     ` Jeremy Yallop
2018-01-23 21:36       ` Chet Murthy
2018-01-23 22:06         ` Jeremy Yallop [this message]
2018-01-23 23:14           ` Hendrik Boom
2018-01-24  1:06             ` Chet Murthy
2018-01-24  1:35             ` Francois BERENGER
2018-02-07  2:00               ` [Caml-list] [ANN] first release of bst: a bisector tree implementation Francois BERENGER
2018-02-07 12:40                 ` Ivan Gotovchits
2018-02-08  0:46                   ` Francois BERENGER
2018-01-24  1:56             ` [Caml-list] Are record types generative? Yawar Amin
2018-01-25 10:49               ` Matej Košík
2018-01-25 13:39                 ` Simon Cruanes
2018-01-25 16:24                 ` Yawar Amin
2018-01-24  1:05           ` Chet Murthy
2018-01-24  8:43             ` Jacques Garrigue
2018-02-02 23:07               ` Toby Kelsey
2018-02-02 23:23                 ` Evgeny Roubinchtein
2018-02-04  1:27                 ` Jacques Garrigue

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='CAAxsn=E5fyfPrtvr6StMRoebAuwOOR7GoBXhz=hbAnpdQG+_Zw@mail.gmail.com' \
    --to=yallop@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=murthy.chet@gmail.com \
    --cc=oleg@okmij.org \
    /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).