You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 1412 Reporter: administrator Status: closed Resolution: fixed Priority: normal Severity: minor Category: ~DO NOT USE (was: OCaml general)
Bug description
Objective Caml version 3.06
class foo = object method get = `Foo end;;
Some type variables are unbound in this type:
class foo : object method get : [> Foo] end The method get has type [> Foo] where .. is unbound
The ellipsis is probably hidden behind the ">" sign. In
which case the error message is a little obscure. If it
means anything else, then it is completely obscure.
Alex
The text was updated successfully, but these errors were encountered:
Some type variables are unbound in this type:
class foo : object method get : [> Foo] end The method get has type [> Foo] where .. is unbound
This was indeed confusing.
The new message is
The method get has type [> `Foo ] as 'a where 'a is unbound
which at least gives an explicit anchor to the problem.
Some type variables are unbound in this type:
class foo : object method get : [> Foo] end The method get has type [> Foo] where .. is unbound
This was indeed confusing.
The new message is
The method get has type [> `Foo ] as 'a where 'a is unbound
which at least gives an explicit anchor to the problem.
Original bug ID: 1412
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Objective Caml version 3.06
class foo = object method get = `Foo end;;
Some type variables are unbound in this type:
class foo : object method get : [>
Foo] end The method get has type [>
Foo] where .. is unboundThe ellipsis is probably hidden behind the ">" sign. In
which case the error message is a little obscure. If it
means anything else, then it is completely obscure.
Alex
The text was updated successfully, but these errors were encountered: