Nicolai Parlog • 8/27/2015

Java 8 SE Optional, a strict approach

Read Original

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
Java 8 SE Optional, a strict approach

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 4 votes
2
Better react-hook-form Smart Form Components
Maarten Hus • 2 votes
3
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
4
Quoting Thariq Shihipar
Simon Willison • 1 votes
5
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes
6
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes