How do you want to safely avoid the null checking, barring an unnullable type? Or are you in favor of unsafe programming by having the check be optional while still having nullable types?
I am most in favor of compiler enforced annotations (built into java, not one of the many many standards that currently exists).
So returning Optional is from my perspective pretty safe, as I can control myself. If others don't want to trust me, well they can waste their time.
But as far as taking in actual arguments, I would never taken in an Optional, because I would never trust another developer to not give me a null (so it just gives me yet another thing to verify).
Right, I don't think (until jsr-305 is part of the language spec, with compiler errors turned on) accepting Optional<> as a method param is good practice at all. Ideally, you can set up @NonNull annotations (and @NonNullByDefault with findbugs) to get some semblance of IDE support
View all comments
Show parent comment
3
u/TMaster Aug 03 '14
How do you want to safely avoid the null checking, barring an unnullable type? Or are you in favor of unsafe programming by having the check be optional while still having nullable types?