Feedback on Null-Restricted and Nullable Types

[Brian S O'Neill]

On 2024-09-10 02:43 PM, Olexandr Rotan wrote:

> I would say that best option 
> would be to introduce compiler flag that enables non-null by default, 
> and eventually, after most users are migrated, make it true by default.

Such a flag would effectively make javac target multiple different 
languages, and there'd be nothing in the source file (or extension) 
which indicates what language you intend to use.

The only sensible flag would be a new lint warning, which can be 
combined with -Werror to fail compilation. Making the warning (and 
failure) a default behavior would be very annoying, and it would break 
compatibility.