Stop checking for nulls in Java

Thanks to original article and writer :

https://towardsdev.com/stop-checking-for-nulls-in-java-593a1f1a0c2f

The biggest problem I had coming back to Java was that I had to deal with the NullPointerException again — not really, you always need to sanitize input and output. Explicitly checking for nulls all the time is going to make your high-level code look lower-level than it is, and your low-level code even harder for others to understand.

For single objects, there are simple ways to deal with it. For example;

Using Objects#nonNull

Or you could use Optional…

And this is all good and readable. But when we are dealing with objects inside objects, things get hideous really fast.

You could try statically importing?Object's?nonNull?method to make it more readable, too.

But this is just a little better. You could also try using?Optional#ofNullable

But that’s still a lot of work. What if you just want to access a value without all these methods in your way? Presenting to you, safeEval:

And this is how you would implement it:

The idea is pretty simple. All you need to do is wrap your get method and if it throws a NullPointerException you catch it. This is not going to be acceptable on every project, though. In this case, I would go for the?Optional#mapapproach.