[GR-51416] AllowAllHostedUsagesClassInitializationSupport.initializeAtBuildTime should eagerly initialize the class #8185
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Time should eagerly initialize the class [GR-51416]
oracle-contributor-agreement
bot
added
the
OCA Verified
zapster
changed the title
|
superseded by #8193 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The legacy class initialization strategy
ProvenSafeClassInitializationSupportinitialized the class eagerly when registered forinitializeAtBuildTime. The new default strategyAllowAllHostedUsagesClassInitializationSupportdid not do this yet. We should change the latter, as we also have other places where we need to mitigate class initialization deadlocks, and that seems like a simple way to do it.