Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P3
Fix Version/s: 8
Affects Version/s: 8
Component/s: core-libs
Labels:
- sqe-testdev-not-needed

Subcomponent:
java.util
Resolved In Build:
b87
CPU:

generic
OS:

generic
Verification:
Verified

In JDK 7, java.util.Objects included several methods to check for null, including one that took a message to return if a null was found. With lambdas in JDK 8, another variant to include is a requireNonNull method which takes a string supplier instead of a string. That why the cost of creating the string message can be avoided for the non-null case. Note that the lambda capture can have a nonzero cost though.

relates to

JDK-8012343 Objects.requireNonNull(Object,Supplier) breaks genstubs build

Closed

JDK-7012540 java.util.Objects.nonNull() incorrectly named

Closed

JDK-6889858 Add nonNull methods to java.util.Objects

Resolved

JDK-8014365 Restore Objects.requireNonNull(T, Supplier<String>)

Closed

JDK-6797535 Add shared two argument static equals method to the platform

Resolved

JDK-8012343 Objects.requireNonNull(Object,Supplier) breaks genstubs build

Closed

JDK-8033909 Objects.requireNonNull(T, Supplier) doesn't specify what happens if the passed supplier is null itself

Closed

(2 relates to)

Assignee:: Joe Darcy

Reporter:: Joe Darcy

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2013-04-09 10:22

Updated:: 2017-05-16 17:20

Resolved:: 2013-04-15 18:35

Details

Description

Attachments

Issue Links

Activity

People

Dates