Open vporton opened 5 months ago
I feel your pain.
(Note to self: to address this properly we have to extend our subtyping check to not just return a bool but, in the failure case, a path indicating which subgoal during subtying failed. Moscow ML does something similar at the module level.)
It is very inconvenient, when I receive a long message of two Actor classes differing. I want the message to show where (which methods with their signatures) is the point(s) of difference.
I adopted to copy the error message, extract from it two Actor classes manually and compare them with
wdiff
command to find what's wrong. But that's inconvenient.