Fix LazyRandom
for native code generation tools
#85
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.
Trying to generate a native code image with GraalVM in code that uses
TimeBasedEpochGenerator
results in this exception:This happens because the
TimeBasedEpochGenerator
constructor initializes theLazyRandom
class unconditionally, even if it is never actually used because the constructor is never passed a nullRandom
instance, andLazyRandom
eagerly creates aSecureRandom
instance in a static final field.Changing the
TimeBasedEpochGenerator
constructor would break backward compatibility, so instead I have opted to modifyLazyRandom
so thatSecureRandom
initialization actually occurs lazily. With this, the code path that results in initializingLazyRandom.shared
is never hit at code generation phase, and so native image generation works as expected.