defender methods and method of Object

Dan Smith daniel.smith at
Mon Mar 12 12:31:29 PDT 2012

On Mar 10, 2012, at 1:01 PM, Neal Gafter wrote:

> On Sat, Mar 10, 2012 at 5:06 AM, David Holmes <david.holmes at> wrote:
> On 10/03/2012 3:56 AM, Dan Smith wrote:
> > Yes, I've been thinking the same thing.  Since the Object methods are morally members of every interface, it would make sense that a default method could effectively override them, and the "throw out all super methods that have already been overridden" rule could then apply.  It all depends on what order the inheritance conflict-resolution rules are applied in.
> If you go down this path then you are throwing away the "superclass
> implementation always wins" rule - in which case what rule are you going
> to replace that with?
> I suspect the rule that Dan is imagining is something like "superclass implementation always wins (except for Object implementation); if none then interface implementation wins; if none then Object implementation wins."

Even simpler, actually.  See "State of the Lambda" [1], section 12, the rules described after "Two basic principles drive these rules..."  What is interesting and unique about the Object methods is that _both_ rules apply, and give different answers.  So one of the two, either "class beats interface" or "overrider beats overridden", has to take priority.

I'm not wholeheartedly endorsing the idea of the "overrider beats overridden" rule having a higher priority, though.  It's plausible, and I like how it fits pretty cleanly into the model, but the model that prefers the "class beats interface" rule is also pretty clean.  The implications of either approach deserve a lot more thought.



More information about the lambda-dev mailing list