Optional.orElse(null) ambiguity

[Joe Bowbeer]

I like:

orElseFrom(Supplier)

I don't like orElseGet(Supplier) because whenever I read orElse(other), I
"translate" it as getOrElse(other).


On Mon, Jan 14, 2013 at 10:23 AM, Brian Goetz <brian.goetz at oracle.com>wrote:

> Null is a valid value for orElse(T) but not for orElse(Supplier).  So we
> care about this ambiguity (there are other similar ones we don't care
> about, when null isn't a valid value for either option.)
>
> orElseNull is a possibility.
>
> Alternately, orElseGet(Supplier) ?  orElseFrom(Supplier)?
>
> On Jan 13, 2013, at 10:00 PM, Joe Bowbeer wrote:
>
> > In b72, optional.orElse(null) is ambiguous because it matches both of
> the orElse forms:
> >
> >  T orElse(T other)
> >  T orElse(Supplier<T> other)
> >
> > For example, this won't compile:
> >
> >  return stream.max(comparator).orElse(null);
> >
> >
> > Optional needs a concise way to return null, so I suggest:
> >
> >  T orElseNull()
> >
> > --Joe
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/lambda-libs-spec-experts/attachments/20130114/f8b25561/attachment.html