Replace proxy runtime init code with "-H:+UseNewExperimentalClassInit… #937
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ialization"
@ppalaga I'm wondering if the -H:+UseNewExperimentalClassInitialization flag is a viable alternative to the Proxy runtime initialization workarounds we put in place. This approach also resolves all the cyclic issues identified in #860 and #916 .
EDIT: Looking closer through all the previous notes on Proxy runtime init, I just stumbled upon #580 (comment) where oracle/graal#4684 was already referenced. I guess I could've saved a couple hours of digging if I had read all of the notes carefully!!
I'm curious why you didn't go with this option, as it seems to be only a matter of time before this becomes the new default in Graal?