From: Alain Frisch <alain@frisch.fr>
To: 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: Thu, 04 Jul 2013 10:14:09 +0200 [thread overview]
Message-ID: <51D52ED1.30808@frisch.fr> (raw)
In-Reply-To: <4AA00D93-1FD9-4E5B-9960-959BA835E8E5@math.nagoya-u.ac.jp>
On 07/04/2013 03:00 AM, Jacques Garrigue wrote:
> In theory, it would be OK to assume that all pattern-matchings may contain GADT type constructors.
> The only real problem is with let's: if they contain GADTs, we must use the code for pattern-matching, which doesn't handle unused definition warnings in the same way… Having all non recursive let's go through this code would have a high impact on warnings.
If this is the only problem with the direct approach (not depending on
backtracking), maybe the treatment of warnings can be parametrized to
behave as expected?
> If unused definition warnings could be separated from type checking this would be much easier.
Maybe I'm wrong, but it seems to me that achieving the same behavior
would require to duplicate of lot of the "data-flow" logic in the
type-checker, thus increasing the global complexity (and the risk to
have diverging behaviors).
Alain
next prev parent reply other threads:[~2013-07-04 8:14 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
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 [this message]
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=51D52ED1.30808@frisch.fr \
--to=alain@frisch.fr \
--cc=caml-list@inria.fr \
--cc=garrigue@math.nagoya-u.ac.jp \
/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).