[Vector API] Utils.isNonCapturingLambda can return false positives.

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: P4
    • tbd
    • Affects Version/s: 26
    • Component/s: core-libs

      When the JVM runs with -Djdk.internal.lambda.disableEagerInitialization=true, non-capturing lambdas get a static final field LAMBDA_INSTANCE$, which holds the singleton instance of that lambda. The presence of this field causes such lambdas to fail the jdk.internal.vm.vector.Utils#isNonCapturingLambda check.

      I ran into this issue when using the Vector API in native-image, where -Djdk.internal.lambda.disableEagerInitialization=true is set by default.

            Assignee:
            Xueming Shen
            Reporter:
            Jiri Marsik
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: