RFR: 8242451: ensure semantics of non-capturing lambdas are preserved independent of execution mode

Mandy Chung mchung at openjdk.java.net
Wed Sep 9 16:43:45 UTC 2020

On Wed, 9 Sep 2020 08:18:11 GMT, Gilles Duboscq <gdub at openjdk.org> wrote:

> [JDK-8232806](https://bugs.openjdk.java.net/browse/JDK-8232806) introduced the
> jdk.internal.lambda.disableEagerInitialization system property to be able to disable eager initialization of lambda
> classes. This was necessary to prevent side effects of class initializers triggered by such initialization in the
> context of the GraalVM native image tool.  However, the change as it is implemented means that the behaviour of
> non-capturing lambdas depends on the value of `disableEagerInitialization`: when it is false (the default) such lambdas
> are actually a singleton while when it is true, a fresh instance is returned every time.  Programs should definitely
> _not_ rely on reference equality since the Java spec does not guarantee it. However, in order to separate concern and
> ease debugging such bad programs, `disableEagerInitialization` shouldn't influence the singleton vs. fresh instance
> behaviour of lambdas in either direction.

Looks good.   I agree with Jan's suggestion that it's good to move the test to test/jdk/java/lang/invoke/lambda which
is a better home for it.


Marked as reviewed by mchung (Reviewer).

PR: https://git.openjdk.java.net/jdk/pull/93

More information about the compiler-dev mailing list