On Wed, 1 Jul 2026 18:39:15 GMT, Alan Bateman <[email protected]> wrote:
>> JVMTI ForceEarlyReturnVoid can be used to return early from a constructor or >> class initializer. Early return from a constructor with strictly-initialized >> instance fields is problematic, as is early return from a class initializer >> when there are strictly-initialized static fields. The proposal for the >> initial integration is to keep it simple and just disallow >> ForceEarlyReturnVoid to return early from a value class constructor. >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Alan Bateman has updated the pull request incrementally with one additional > commit since the last revision: > > Add more qualifcation to examples in OPAQUE_FRAME error Nice spec tweaks and new test cases. Looks good. There is one typo in a comment. test/hotspot/jtreg/serviceability/jvmti/ForceEarlyReturn/ForceEarlyReturnValueClass.java line 157: > 155: thread.join(); > 156: } > 157: assertFalse(TestCase.postInitFinished); // postInit should not > have run to the end Nit: A typo in the comment: s/postInit should not/postInit should/ ------------- Marked as reviewed by sspitsyn (Committer). PR Review: https://git.openjdk.org/valhalla/pull/2604#pullrequestreview-4612153147 PR Review Comment: https://git.openjdk.org/valhalla/pull/2604#discussion_r3508423808
