Incorrect interface methods in Project.instanceMethods

Project.interfaceMethods may contain methods from directly implemented interfaces even if they are not the maximally specific interface method (this may happen if a class declares to implement two interfaces that are in a subtype relationship).

Additionally, Project.instanceMethods fails to recognize when a default method inherited from a superclass is abstractly overwritten by a more specific interface. In that case, the method should presumably be abstract (i.e. not in instanceMethods for the current type) as the abstract method is the maximally specific interface method.

Comments (3)