Java, null, and JSpecify

[@bkoprucu]

Well thought out approach to the enduring null problem. This should succeed. I'll give it a try.

[@chrispie5]

Aweseome approach. Any maven/gradle examples to play with it and see how the setup is done?

[@TheBigLou13]

Integer i = 0; // nullable int i = 0; // not nullable

[@creamycoffee]

Now do that with String.

[@TheBigLou13]

​@@creamycoffee ​​​int is the same as char. String is the same as char array. Arrays have dynamic length and can be null. If you work with non-primitive data types like that use Optional - its made for that purpose. If you run into Optionals being null you're using them wrong: You should never receive (nullable) Optionals - instead, when you receive (nullable) non-primitive data, you can wrap them in an Optional before using them, e.g. using Optional.of(...);

[@juancarlospizarromendez3954]

null.equals(null) gives me true; this = equal; this.equals(null) gives me true; that's a technical joke!

[@TheBigLou13]

null.equals() returns a NullPointerException because you're literally pointing to a null and calling a method on it. You're pointing at the absence of something and ask it to do something. That doesn't make sense. You *_can_* check if ( null == null ).

[@JorgetePanete]

I would love some flag like "nonullness", that without annotations makes everything non-nullable

[@TheBigLou13]

String notNull = Optional.of(nullable).orElse("ValueIfNull");

[@JorgetePanete]

@@TheBigLou13 Yeah, without putting that everywhere

[@steshaw6510]

They call it @NullMarked. You can put the annotation at the package or module level.