3 ms·
Eh, I think it is good in Java in cases where Null input is possible.
by brianwawok 10y ago
Eh, I think it is good in Java in cases where Null input is possible.
- paol 10y agoYes, "foo".equals(bar) is useful in Java if bar can be null, but that's a different thing.
- brianwawok 10y agoNot really different. In fact is is mentioned on the Wikipedia page.
- PaulHoule 10y agoI think it is better than if(x!=null && x.equals("y") You have to take bits of concision where you can find them in Java.
- deleted 10y ago[deleted]
- megawatthours 10y agoI never got the Java argument. I would much rather fail early and noisily with an NPE than return false and let my program happily chug along when it wasn't expecting a null. If the value is intended to be nullable, I would use an optional.
- xxs 10y agoJava8 optional is way slower (write a tree alike struct with optional for left/right/parent) and null checks are one of the free ones. (Hardware optimized)
- brianwawok 10y agoWell for 95% of Java's live, there was no such thing as Optional. So say untrusted user input.. many cases where it could be something or null. Yoda checking it was a nice way to save a null check.