Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Alain Frisch <alain@frisch.fr>
To: Yannis Juglaret <yjuglaret@gmail.com>, caml-list@inria.fr
Subject: Re: [Caml-list] Matching exhausitvity with GADT and modules
Date: Wed, 27 May 2015 22:22:06 +0200	[thread overview]
Message-ID: <5566276E.7040701@frisch.fr> (raw)
In-Reply-To: <5565E49B.9090209@gmail.com>

On 27/05/2015 17:36, Yannis Juglaret wrote:
> This is a question to the list: is there any good reason for allowing
> abstract types in module implementations, and not just in module
> signatures -- where they can actually be used to abstract types?

Abstract types in structures can be used to represent opaque foreign 
values manipulated through the FFI (typically custom blocks, or blocks 
which cannot -- or need not -- be described as OCaml types).


Alain

  reply	other threads:[~2015-05-27 20:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 15:04 Joris Giovannangeli
2015-05-27 15:14 ` Ben Millwood
2015-05-27 15:22   ` Joris Giovannangeli
2015-05-27 15:36     ` Yannis Juglaret
2015-05-27 20:22       ` Alain Frisch [this message]
2015-05-27 15:43   ` Arseniy Alekseyev

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=5566276E.7040701@frisch.fr \
    --to=alain@frisch.fr \
    --cc=caml-list@inria.fr \
    --cc=yjuglaret@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