caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Romain Bardou <romain@bardou.fr>
To: Jeremy Yallop <yallop@gmail.com>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Why doesn't relaxed value restriction apply here?
Date: Sat, 21 Apr 2018 11:14:59 +0200	[thread overview]
Message-ID: <f9f5f020-8d01-c5f6-74bf-ccb3ba49f256@bardou.fr> (raw)
In-Reply-To: <CAAxsn=F1RAp=jGiy9Ge9CW0inm9bm45X0c_6GLrZbrtwH2U3nw@mail.gmail.com>

On 04/21/2018 11:04 AM, Jeremy Yallop wrote:
> On 21 April 2018 at 09:41, Romain Bardou <romain@bardou.fr> wrote:
>> According to the manual
>> (http://caml.inria.fr/pub/docs/manual-ocaml/polymorphism.html) and to the
>> paper "Relaxing the Value Restriction"
>> (http://caml.inria.fr/pub/papers/garrigue-value_restriction-fiwflp04.pdf),
>> the relaxed value restriction allows to generalize type variables which only
>> appear in covariant positions.
>>
>> The following code :
>>
>>      let f = let _ = ref 0 in fun f -> f []
>>
>> returns the following in the toplevel:
>>
>>      val f : ('_a list -> '_b) -> '_b = <fun>
>>
>> In this type, '_a only appears in covariant position. So, why is it not
>> generalized?
> 
> I think the current implementation only generalizes variables that
> only occur in *strictly* positive positions -- that is, that do not
> appear to the left of any arrow.  In your example, "'a" occurs in a
> positive position (to the left of an even number of arrows) that is
> not strictly positive (to the left of zero arrows).

Interesting. I wonder what the reason is behind this choice: is it about 
soundness, or about simplicity. Your example below seems to indicate 
that this is not about soundness as one can hide the depth of a type 
variable using an abstract type.

> This choice can lead to some slightly surprising situations, where
> exposing valid type equalities can cause previously-valid programs to
> be rejected.  For example, the following program, which is based on
> your example, is accepted:
> 
>     module M :
>     sig
>       type (+'a,'b) t
>       val g : unit -> ('a,'b) t
>     end =
>     struct
>       type (+'a,'b) t = ('a list -> 'b) -> 'b
>       let g () = let _ = ref 0 in fun f -> f []
>     end;;
> 
>     let f = M.g () in ((f : (int, unit) M.t), (f : (float, unit) M.t));;
> 
> but if the signature for 'M' is removed then the program is rejected.

That's very interesting actually.

Thanks a lot for your quick answer and your example :)

Cheers,

-- Romain Bardou

-- 
Caml-list mailing list.  Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs

  reply	other threads:[~2018-04-21  9:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-21  8:41 Romain Bardou
2018-04-21  9:04 ` Jeremy Yallop
2018-04-21  9:14   ` Romain Bardou [this message]
2018-04-21  9:45     ` Jeremy Yallop
2018-04-21 11:34       ` Romain Bardou

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=f9f5f020-8d01-c5f6-74bf-ccb3ba49f256@bardou.fr \
    --to=romain@bardou.fr \
    --cc=caml-list@inria.fr \
    --cc=yallop@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).