Optional.or() doesn't use a wildcard in its signature (original) (raw)
Vitaly Davidovich vitalyd at gmail.com
Sat Oct 31 18:59:00 UTC 2015
- Previous message: Optional.or() doesn't use a wildcard in its signature
- Next message: Optional.or() doesn't use a wildcard in its signature
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
This would require Supplier<Optional<? extends T>>, not Supplier<? extends Optional>.
sent from my phone On Oct 31, 2015 2:49 PM, "Michael Nascimento" <misterm at gmail.com> wrote:
If this instance is an Optional , passing an Optional will fail to compile.
Regards, Michael On 31 Oct 2015 11:21, "Stefan Zobel" <spliterator at gmail.com> wrote: > 2015-10-31 19:11 GMT+01:00 Remi Forax <forax at univ-mlv.fr>: > > > Hi all, hi Paul, > > > > I've just seen that Optional.or is declared as > > public Optional or(Supplier<Optional> supplier) { > > instead of > > public Optional or(Supplier<? extends Optional> supplier) { > > > > regards, > > Rémi > > > > > I don't get it. Optional is final anyway. Can you explain? > > Thanks, > Stefan >
- Previous message: Optional.or() doesn't use a wildcard in its signature
- Next message: Optional.or() doesn't use a wildcard in its signature
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]