From: Goswin von Brederlow <goswin-v-b@web.de>
To: Dmitri Boulytchev <dboulytchev@gmail.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Confusing behaviour of type inference for polymorphic classes.
Date: Mon, 2 Dec 2013 15:41:01 +0100 [thread overview]
Message-ID: <20131202144100.GA24602@frosties> (raw)
In-Reply-To: <529BAB43.3080105@gmail.com>
On Mon, Dec 02, 2013 at 01:33:55AM +0400, Dmitri Boulytchev wrote:
> Hello everyone,
>
> I stumbled on the following confusing behaviour of the type
> checker: given the definitions
>
> type ('a, 'b) t =
> A of 'a * ('b, 'a) t
> | B of 'a
>
> class ['a, 'b, 'ta, 'tb] m =
> object
> method t : ('a -> 'ta) -> ('b -> 'tb) -> ('a, 'b) t -> ('ta,
> 'tb) t =
> fun fa fb s ->
> match s with
> | A (a, bat) -> A (fa a, (new m)#t fb fa bat)
> | B a -> B (fa a)
> end
>
> the following type is inferred for the class m:
>
> class ['a, 'b, 'ta, 'c] m :
> object
> constraint 'b = 'a <--- why?
> constraint 'c = 'ta <--- why?
> method t : ('a -> 'ta) -> ('a -> 'ta) -> ('a, 'a) t -> ('ta, 'ta) t
> end
I think this is caused by the recursion. The type inference assumes
that the recursive call will have the same type as the parent. Since
you switch 'a and 'b in the recursive call the compiler inferes that
'a == 'b.
> Perhaps some explicit annotation is needed here (like that for
> the polymorphic recursion
> for functions).
> I found the following workaround: first we abstract the instance
> creation ("new m") away:
>
> class ['a, 'b, 'ta, 'tb] m' f =
> object
> method t : ('a -> 'ta) -> ('b -> 'tb) -> ('a, 'b) t -> ('ta,
> 'tb) t =
> fun fa fb s ->
> match s with
> | A (a, bat) -> A (fa a, (f ())#t fb fa bat)
> | B a -> B (fa a)
> end
>
> which gives us the unconstrained type
>
> class ['a, 'b, 'ta, 'tb] m' :
> (unit ->
> < t : ('b -> 'tb) -> ('a -> 'ta) -> ('b, 'a) t -> ('tb,
> 'ta) t; .. >) ->
> object
> method t : ('a -> 'ta) -> ('b -> 'tb) -> ('a, 'b) t ->
> ('ta, 'tb) t
> end
>
> Then we construct the instance creation explicitly polymorphic function:
>
> let rec f : 'a 'b 'ta 'tb . unit -> <t : ('a -> 'ta) -> ('b ->
> 'tb) -> ('a, 'b) t -> ('ta, 'tb) t> =
> fun () -> new m' f
>
> and finally the class we're looking for:
>
> class ['a, 'b, 'ta, 'tb] m = ['a, 'b, 'ta, 'tb] m' f
>
> The complete annotated source file is attached.
> This workaround however does not solve everything: we cannot
> actually inherit
> from the m since it calls hardcoded "new m"; we should inherit from
> m' (with additional parameter)
> instead and "tie the knot" on the toplevel.
> Are there better solutions? Please help :)
Try using a self type or #m but this might not be solvable.
> Best regards,
> Dmitry Boulytchev,
> St.Petersburg State University,
> Russia.
MfG
Goswin
next prev parent reply other threads:[~2013-12-02 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 21:33 Dmitri Boulytchev
2013-12-02 14:41 ` Goswin von Brederlow [this message]
2013-12-02 15:05 ` Dmitri Boulytchev
2013-12-05 15:13 ` Goswin von Brederlow
2013-12-02 15:24 ` Jeremy Yallop
2013-12-03 8:35 ` Alain Frisch
2013-12-03 10:17 ` Jeremy Yallop
2013-12-03 12:33 ` Alain Frisch
2013-12-03 12:58 ` Jeremy Yallop
2013-12-03 17:49 ` Dmitri Boulytchev
2013-12-08 1:15 ` Jeremy Yallop
2013-12-09 13:48 ` Dmitri Boulytchev
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=20131202144100.GA24602@frosties \
--to=goswin-v-b@web.de \
--cc=caml-list@inria.fr \
--cc=dboulytchev@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