> Why not use JSpecify[1] instead? It is not perfect (e.g. there is no > official list of tools that support it[2]), but it has many commercial > supporters and it might become what JSR305 failed to be.
I tend to use jetbrains annotation as JSR305 impl and extension in my own repo if you ask. Just, I personally treat JSpecify, jb annotatins, checkframe or something more or less JSR305 impl and extensions... I'm glad to accept anything that just can let us mark nonnull & nullable... Piotr P. Karwasz <pi...@mailing.copernik.eu> 于2025年2月11日周二 22:45写道： > Hi Xeno, > > On 11.02.2025 05:35, Xeno Amess wrote: > > during recently learning about maven and maven-resolver, sometimes I > really > > think it better to have nullable/notnull annotations... > > Why not use JSpecify[1] instead? It is not perfect (e.g. there is no > official list of tools that support it[2]), but it has many commercial > supporters and it might become what JSR305 failed to be. > > Piotr > > [1] https://jspecify.dev/ > > [2] https://github.com/jspecify/jspecify/issues/688 >
