JDK-8025100 : Use j.u.Object.requireNonNull in j.l.invoke codebase
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.lang.invoke
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2013-09-19
  • Updated: 2015-03-06
  • Resolved: 2015-03-06
Related Reports
Duplicate :  
JDK-8073479 - Replace obj.getClass hacks with Objects.requireNonNull
Relates :  
JDK-7041258 - Use j.u.Object.requireNonNull in the JDK codebase
Description
The current usage for explicit null checks in j.l.invoke is "x.getClass()", which relies on a JIT intrinsic to get the desired performance and compactness.

It appears likely the j.u.Objects.requireNonNull will provide the same performance and compactness, with improved startup time.

This RFE tracks this change, to help with performance testing.
Comments
This refactoring to java.lang.invoke was done under JDK-8073479. Closing as a duplicate.
06-03-2015