On Oct 3, 2018, at 3:56 PM, Alex Buckley <alex.buck...@oracle.com> wrote: > > Let's say that Java 5 had the right idea by coupling an overriding method to > an overridden method, via @Override. Then, your proposal is at odds with Java > 5, because omitting the method signature of the overriding method also means > omitting @Override. (I assume you intended for there to be no annotations on > your lambda-like method bodies such as `hashNext() -> index < end;`)
Put another way, Remi's suggestion is for a coupling stronger than @Override, which is purely advisory. An 'override' modifier would upgrade the advice to something mandatory, at which point types might from from the super. Not saying this is a good idea, just pointing out that @Override provides a *weak partial* precedent for pulling schema from the super.
