From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: Alain.Frisch@inria.fr
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Type constraints
Date: Wed, 08 Dec 2004 23:23:22 +0900 (JST) [thread overview]
Message-ID: <20041208.232322.07401394.garrigue@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <41B6F610.8000507@inria.fr>
From: Alain Frisch <Alain.Frisch@inria.fr>
> Damien Doligez wrote:
> > Hmmm... Now I don't know whether it's safe or not, and I don't know
> > whether someone checked its safety before excluding it from the value
> > restriction code...
>
> With this extra line added to is_nonexpansive:
>
> | Texp_letmodule (_,_,e) -> is_nonexpansive e
>
> we get:
>
> # let module M = struct let x = ref [] end in M.x;;
> - : 'a list ref = {contents = []}
>
> The non-generalizable status has been forgotten. What I'm not sure is
> whether this is only an artefact of the internal representation of
> levels to control generalization, or whether there are some deeper issues.
It's not really an artefact, just that there is no such thing as a
non-generalizable status: something that is not generalizable in some
context becomes generalizable in a larger context.
So you cannot rely on the generalizability obtained during the typing
of the module. Rather you must check whether the module
itself contains only non-expansive definitions. I.e. you cannot ignore
the definition of the module, as you are doing here.
Yet, modules are strange beasts for typing, so I wouldn't add the code
before thinking it through.
(Note that there is another way to handle non-generalizability,
without relying on a non-expansiveness predicate, raising the
non-generalizable level only when entering functions, and that might
solve the problem for free. Francois Pottier told me he was using
it. However it requires many small changes to type inference, and
doesn't mix well with the new "relaxed" value restriction.)
Jacques Garrigue
next prev parent reply other threads:[~2004-12-08 14:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 19:55 Jim Farrand
2004-12-07 7:12 ` [Caml-list] " Alain Frisch
2004-12-07 13:43 ` Damien Doligez
2004-12-07 14:57 ` Andreas Rossberg
2004-12-07 17:44 ` Damien Doligez
2004-12-07 18:08 ` Alain Frisch
2004-12-07 21:04 ` Damien Doligez
2004-12-07 21:43 ` Alain Frisch
2004-12-08 3:30 ` nakata keiko
[not found] ` <8002B033-4906-11D9-8195-000D9345235C@inria.fr>
2004-12-09 0:56 ` nakata keiko
2004-12-09 1:27 ` Jacques Garrigue
2004-12-08 10:53 ` Damien Doligez
2004-12-08 12:39 ` Alain Frisch
2004-12-08 14:23 ` Jacques Garrigue [this message]
2004-12-09 3:07 ` skaller
2004-12-09 4:53 ` Jacques Garrigue
2004-12-08 16:10 ` Xavier Leroy
2004-12-07 18:13 ` William Lovas
2004-12-08 0:27 ` Jacques Garrigue
2004-12-07 18:41 ` Boris Yakobowski
2004-12-07 19:38 ` Jim Farrand
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=20041208.232322.07401394.garrigue@math.nagoya-u.ac.jp \
--to=garrigue@math.nagoya-u.ac.jp \
--cc=Alain.Frisch@inria.fr \
--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).