Nicolai Parlog • 8/27/2015

Java 8 SE Optional, a strict approach

This technical article presents a counter-argument to Stephen Colebourne's pragmatic approach for using Java 8's Optional class. The author disagrees with the common recommendation that Optional should only be used as a return type, and instead advocates for a stricter, more consistent application throughout code, including as fields and method parameters, to improve null safety and design clarity.

0 comments

#api design #functional programming #Java