Adam Gent

> and even if we automate, I think I'd still rather not see all those package-info.java in the directory tree... I'm just saying you should give it a try because...

NullUnmarked is your best bet. You are right that is technically not the same but I think it effectively works out to be mostly the negation of NullMarked. BTW If...

> > BTW If this is new code I highly recommend you do not follow that pattern of nullable in and nullable out especially for public methods. > > @agentgt...

> I disagree with this. If the method is called 100 times, why burden each caller with checking for null when I could put that logic inside the method (once)...

@cpovirk was I correct in saying that it is up to the tool to decide or not to fail where @donalmurtagh potential npe comment is? ```java @NullUnmarked public class ResourceConverters...

I think I had a conversation with @msridhar about something similar: > agentgt — 07/26/2024 2:10 PM A useful feature that maybe you guys already have is to detect if...

> I think the spec only requires 1. Technically we could not do 2 and require a separate @SuppressWarnings annotation, but we did not decide to do that. Eventually we...

> (I'll also say that this is another case in which nullness will feel a lot less burdensome if it becomes possible to write "Foo?" instead of "@Nullable Foo." Hopefully...

> > (btw if Kevin sees this I can't signup for project Loom's mailinglist for some reason but it would be great if they do not add PolyNull `orElse` to...