From: Alain Frisch <alain@frisch.fr>
To: Jacques Le Normand <rathereasy@gmail.com>,
Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: OCaML List Mailing <caml-list@inria.fr>
Subject: Re: [Caml-list] Request for feedback: A problem with injectivity and GADTs
Date: Mon, 29 Apr 2013 09:58:16 +0200 [thread overview]
Message-ID: <517E2818.5040506@frisch.fr> (raw)
In-Reply-To: <CAK0y-36uPAAXGanrhZKQOQAPsELjTFxM1Av820da-mU4kqTVfg@mail.gmail.com>
On 04/29/2013 07:17 AM, Jacques Le Normand wrote:
> Fully injective types are the norm. It would have been nice to have a
> "non injectivity" or "phantom type" annotation. Since phantom types are
> seldom used, beginners won't get confused. It might even help beginners
> understand the concept of a phantom type.
I'd also prefer an annotation on "non injective" type parameters, rather
than on "injective" one. The problem with this approach is that it
requires existing well-typed code to be rewritten, to add these
annotations (while annotating injectivity will only impact code using
GADTs). I still believe this is less intrusive than requiring most
parametrized abstract type to be annotated, or else making GADTs less
useful.
For the transition, we could have two compilation modes (decided on the
command-line) for this feature. In "non-injective" (legacy) mode, every
parametrized abstract type would be assumed to be non-injective. This
would allow to compile existing code bases (at least those not relying
on GADTs). In "injective-by-default" mode, non-injective parameters
would need to be marked as such. Enabling this mode will require a few
annotations to be added to existing code, but this will be very easy, so
I guess we don't need to support "injectivity" annotations the
"non-injective" mode.
Alain
next prev parent reply other threads:[~2013-04-29 7:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 0:02 Jacques Garrigue
2013-04-28 2:45 ` Markus Mottl
2013-04-28 10:28 ` Jacques Garrigue
2013-04-28 5:54 ` Jacques Le Normand
2013-04-29 3:45 ` Ivan Gotovchits
2013-04-29 4:03 ` Ivan Gotovchits
2013-04-29 5:17 ` Jacques Le Normand
2013-04-29 7:58 ` Alain Frisch [this message]
2013-04-29 10:52 ` Jacques Garrigue
2013-04-29 11:23 ` Alain Frisch
2013-04-29 16:37 ` Nathan Mishra Linger
2013-04-29 23:53 ` Jacques Garrigue
2013-04-30 5:45 ` Jacques Garrigue
2013-05-04 6:46 ` Jacques Garrigue
2013-05-04 7:09 ` Gabriel Scherer
2013-05-04 12:28 ` Jacques Garrigue
2013-04-30 6:59 ` Alain Frisch
2013-04-30 7:56 ` Jacques Garrigue
2013-04-30 8:02 ` Alain Frisch
2013-04-30 8:18 ` Jacques Garrigue
2013-04-30 9:11 ` Gabriel Scherer
2013-04-30 9:55 ` Jacques Garrigue
2013-04-30 10:12 ` Leo White
2013-04-30 11:30 ` Gabriel Scherer
2013-04-30 13:06 ` Leo White
2013-04-29 7:59 ` Gabriel Scherer
2013-07-01 14:47 ` Alain Frisch
2013-07-01 23:20 ` Jacques Garrigue
2013-07-03 16:08 ` Alain Frisch
2013-07-03 16:13 ` Gabriel Scherer
2013-07-04 6:07 ` [Caml-list] Request for feedback: A problem with injectivity oleg
2013-07-04 7:35 ` Alain Frisch
2013-07-05 10:30 ` oleg
2013-07-05 12:02 ` Alain Frisch
2013-07-04 1:00 ` [Caml-list] Request for feedback: A problem with injectivity and GADTs Jacques Garrigue
2013-07-04 8:14 ` Alain Frisch
2013-07-04 8:52 ` 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=517E2818.5040506@frisch.fr \
--to=alain@frisch.fr \
--cc=caml-list@inria.fr \
--cc=garrigue@math.nagoya-u.ac.jp \
--cc=rathereasy@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;
as well as URLs for NNTP newsgroup(s).