Comment author: @yallop

Here's a similar example without a refutation pattern that causes the same assertion failure:

type (,) eql = Refl : ('a, 'a) eql
let f : type t. ((int, t) eql * (t, string) eql) option -> unit =
function None -> ()

Comment author: @garrigue

Fixed in 4.04 by commit babad14.

The problem is that the new exhaustiveness check means that we may have to type GADT constructors even when they do not appear in the patterns themselves.
The fix is to prepare for this expect in cases where this is trivially not needed, i.e. if we just match on a variable and this is not a refutation case. But this means we still do it when matching on unit for instance...

Comment author: @nojb

We are experiencing some regression due to commit babad14. The affected code in question uses object types and type constrains extensively and we are now seeing "Self type cannot escape its class" errors. I am trying to produce a small example, but have not had any luck yet.

I am posting this just to get the word out.

Comment author: @garrigue

This may be related to #7298, making it happen more often.
I shall look into that.
An example would be welcome, whatever its size.

Comment author: @garrigue

#7298 has been fixed in the 4.04 branch. Could you check whether it solves your problem?

Comment author: @nojb

Unfortunately, it does not. I will be looking at this today and will try to get back with more information/an example.

Comment author: @nojb

Small repro:

class virtual child1 parent =
object
method private parent = parent
end

class virtual child2 =
object(_ : 'self)
constraint 'parent = < previous: 'self option; .. >
method private virtual parent: 'parent
end

let _ =
object(self)
method previous = None
method child =
object
inherit child1 self
inherit child2
end
end

Error: The method parent has type < child : 'a; previous : 'b option >
but is expected to have type < previous : < .. > option; .. >
Self type cannot escape its class

Comment author: @garrigue

I see.
You're using a nested immediate object referring to the outer self.
This is probably not well supported at this point (independently of commit babad14).
I'm not sure I will be able to fix it for 4.04.
Also, this is a new issue, so could you file a new bug report?

A workaround for this example is to move the inner object outside, so that its parameter is generalized:

let _ =
let child self =
object
inherit child1 self
inherit child2
end
in
object(self)
method previous = None
method child = child self
end

Comment author: @nojb

Thanks for the quick reply.

Filed a new bug report at #7391.

We actually have quite a bit of code using this style so in the meantime it might be simpler for us to revert the last couple of commits rather than rewrite it...