Rather -0 on my side by experience cause this kind of tool is often abused,
in particular using an IoC or a codebase with indirections like maven. One
prerequisite being all the stack uses it - plexus, sisu, commons etc - Im
not sure we can get the benefits without the downsides.
That said you can
I'd prefer not. Every additional dependency we add is a liability.
It's not clear we need something like this and even if we do, JSpecify
is only a few months old. This is only the latest of many efforts to
establish a standard for nullness annotations. I don't see why
JSpecify will be the one ring
