Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8025100

Use j.u.Object.requireNonNull in j.l.invoke codebase

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Duplicate
    • Icon: P3 P3
    • None
    • None
    • core-libs
    • None

      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.

            jrose John Rose
            jrose John Rose
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: