caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Andrej Bauer <andrej.bauer@andrej.com>
To: caml <caml-list@inria.fr>
Subject: Re: [Caml-list] Proposal for extensible open datatypes
Date: Fri, 6 Jan 2012 07:26:19 +0100	[thread overview]
Message-ID: <CAB0nkh3X0zKANrgLm6NFrDVajtRxcxM=DgCe+PN66P9niog79w@mail.gmail.com> (raw)
In-Reply-To: <Prayer.1.3.4.1201060032070.9235@hermes-2.csi.cam.ac.uk>

I would be interested to hear what propeties of Ocaml you had to give
up to get this interesting extension working? For example, what
happens with checking for exhaustivness of match? Caml performs
various optimizations in pattern matching, why are those still ok now
that new alternatives may appear later?

With kind regards,

Andrej

  reply	other threads:[~2012-01-06  6:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06  0:32 Leo P White
2012-01-06  6:26 ` Andrej Bauer [this message]
2012-01-06  8:56   ` Andreas Rossberg
2012-01-06  9:24     ` Leo P White

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='CAB0nkh3X0zKANrgLm6NFrDVajtRxcxM=DgCe+PN66P9niog79w@mail.gmail.com' \
    --to=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).