From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: OCaML List Mailing <caml-list@inria.fr>
Subject: Re: [Caml-list] Request for feedback: A problem with injectivity and GADTs
Date: Tue, 30 Apr 2013 14:45:03 +0900 [thread overview]
Message-ID: <0BC2A384-6D0F-49F2-BD68-5C840BA0888A@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <1EA5B7CE-C0C3-4113-9F8F-C4C3BC888D49@math.nagoya-u.ac.jp>
I have now committed in trunk a fix to PR#5985.
You can use it to test whether your codebase runs into problems.
You can either obtain it from subversion directly
svn checkout http://caml.inria.fr/svn/ocaml/trunk
or use opam to do it for you.
I checked that at least Core itself compiles without problems.
Again, if you run into problems, you can try branches/non-vanishing,
which allows you to annotate some abstract types are injective.
Jacques Garrigue
On 2013/04/29, at 19:52, Jacques Garrigue <garrigue@math.nagoya-u.ac.jp> wrote:
> Dear Camlers,
>
> First, let me reiterate my request for feedback:
>
> What I want to know is whether anybody is using GADTs in a way that
> would be broken if we disallow type variables under abstract types
> (other than the predefined ones) in the return type of GADTs.
> I.e., for instance defining a type witness type involving such abstract types.
>
> This is really the question I want you all to answer.
>
> If this is not the case, we can safely prohibit that at this point, and take
> our time to think about the solution.
next prev parent reply other threads:[~2013-04-30 5:45 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
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 [this message]
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=0BC2A384-6D0F-49F2-BD68-5C840BA0888A@math.nagoya-u.ac.jp \
--to=garrigue@math.nagoya-u.ac.jp \
--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