Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Deprecating: java.util.Optional.get()?. Parent comment
As long as Optional#isPresent exists, you can have "concrete expectations" of an optional's content (or lack thereof).
> At that point a harmless looking refactor by someone else can introduce NPEs.
The fundamental problem is not .get, it's that you're qualifying code changes involving partial function as "harmless-looking" and "refactoring"
There are no comments on this comment yet.
As long as Optional#isPresent exists, you can have "concrete expectations" of an optional's content (or lack thereof).
> At that point a harmless looking refactor by someone else can introduce NPEs.
The fundamental problem is not .get, it's that you're qualifying code changes involving partial function as "harmless-looking" and "refactoring"