My $0.02: This is an easy call. The answer is that it's not worth changing because (b) this would cause legacy to to start failing to compile, which is violates Java's stellar reputation for backward compatibility, and (b) there is already a perfectly reasonable workaround, i.e. -Xlint:static -Werror.
I can't think of very many examples in the past. where Java made such a change (that is, where (a) and (b) were true. I guess the treatment of "_" and "yield" count. -Archie On Fri, Jan 23, 2026 at 6:43 AM Amazing Code <[email protected]> wrote: > I am writing to propose a language enhancement regarding the handling of > static member access in Java. > -- Archie L. Cobbs
