Static method access dilemma and proposal: @NotInherited

[Daniel Latrémolière]

> Anything that moves us towards being able to fix this problem
> over time is good.
Is a new compiler switch "-nodefaults" possible for helping removal 
(step by step) of unsuitable Java defaults?

In this case, you can call javac with this switch and obtain 
supplemental errors/warnings for bad behaviour (default constructor, 
default imports, static method call for superclass, etc.).