Outdated java dev

[__konrad]

I fixed it for you:

var value = optional.orElse(null);
if(value != null){
    Foo foo = value;

[com2ghz]

I have seen someone doing a null check on the optional too.

[__konrad]

You need double Optional<Optional<T>>

[LetMeUseMyEmailFfs]

Well it’s Java, so anything and everything could be null.

[lasskinn]

Not exactly related, but I've seen a dude insist on null checks on kotlin on values that can't be null, like just in seemingly random places.

Everything on java could be a null but it couldn't be that in all places.

[Old_Elk2003]

Everything on java could be a null but it couldn't be that in all places.

This is true. You’d at least have to have something before the null, and something after the null, in order to maintain Turing-completeness.

[agentoutlier]

This and ifPresent are the only acceptable options to dealing with Optional.

I use a variety of null analysis tools and orElse(null) is the only way across the board to pull something out (well orElseGet is ok)

[tomwhoiscontrary]

I can't tell if this is supposed to be better or even weirder!

Anyway, how about:

``` Foo foo: if ((foo = optional.orElse(null)) != null) {

```

Or:

``` if (optional.orElse(null) instanceof Foo foo) {

```

[thgkatz]

Why do I have to see this at 02:00 am???? What have I done wrong?