Eclipse Community Forums: Java Development Tools (JDT) » NonNull and java.lang.Optional orElse()

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » NonNull and java.lang.Optional orElse()

Show: Today's Messages :: Show Polls :: Message Navigator

NonNull and java.lang.Optional orElse() [message #1749868]

Tue, 13 December 2016 11:36

Frank Benoit

Messages: 179
Registered: July 2009

Senior Member

Hi

To just accept a null in case a Option is empty, you can use

Optional<String> opt = ....;
@NonNull str1 = "str1";
@Nullable str2 = read();

@Nullable String res0 = opt.orElse(null);
@NonNull String res1 = opt.orElse(str1);
@Nullable String res2 = opt.orElse(str2);

Is there a way to make this work?
Or would it be needed to ask for a new method in Optional, e.g. orElseNullable(), orNull() ?

Frank

Report message to a moderator

Re: NonNull and java.lang.Optional orElse() [message #1749877 is a reply to message #1749868]

Tue, 13 December 2016 13:42

Stephan Herrmann

Messages: 1853
Registered: July 2009

Senior Member

In class Checks we provide a solution for the first variant:

public static <T> @Nullable T asNullable(@NonNull Optional<T> optional)

Providing a nullable fallback is not supported. Is that really a useful pattern? What's the use of the fallback when it cannot be relied upon itself?

Stephan

Report message to a moderator

Re: NonNull and java.lang.Optional orElse() [message #1750180 is a reply to message #1749877]

Fri, 16 December 2016 19:53

Frank Benoit

Messages: 179
Registered: July 2009

Senior Member

Hi Stephan,

If there would be a way to say "the return nullability is the same as the one of the first parameter", this would solve it perfectly.

But as i understand, with Check.asNullable, I can annotation
@NonNull T Optional.orElse( @NonNull T t )
and replace those places where I used orElse(null) with the Check.asNullable.

thanks
Frank

Report message to a moderator

Re: NonNull and java.lang.Optional orElse() [message #1750219 is a reply to message #1750180]

Sun, 18 December 2016 22:12

Stephan Herrmann

Messages: 1853
Registered: July 2009

Senior Member

do you envision s.t. like

<T> T fromOptionalOrElse(@NonNull Optional<@NonNull T> optional, T fallback)

Here <T> could be either a nullable or a nonnull type - to be inferred from fallback and the target type, whereas the optional would use the nonnull variant of this type.

Still I don't understand whether/why you want a nullable fallback.

Report message to a moderator

Previous Topic:	Null annotation with generated code
Next Topic:	Setting breakpoints in foreign sources

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 03:26:27 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter