> Our intention was to provide a limited mechanism for library method return types where there needed to be a clear way to represent "no result", and using null for such was overwhelmingly likely to cause errors
> Our intention was to provide a limited mechanism for library method return types where there needed to be a clear way to represent "no result", and using null for such was overwhelmingly likely to cause errors
Brian Goetz
да я вот тоже читал это, но как-то это что-то блин.... ну и тогда не надо говорить что orElse(null) - это антипаттерн