JDK 16 RFR of JDK-8071961: Add javac lint warning when a default constructor is created

Jonathan Gibbons jonathan.gibbons at oracle.com
Mon Aug 17 21:18:38 UTC 2020

On 8/17/20 9:29 AM, Alex Buckley wrote:
> compiler.warn.missing-explicit-ctor=\
> class {0} in exported package {1} declares no explicit constructors, 
> exposing a default constructor to clients of module {2} 

Is it just me, or does "declares no explicit constructors" sound weirdly 
stilted, as compared to something like "does not declare any explicit 
constructors" or "does not explicitly declare any constructors".

I'm not suggesting to change the meaning of what is being suggested; I'm 
just trying to find a better phrasing that sounds more natural.

-- Jon

More information about the compiler-dev mailing list