Fix 2396b: Non-static synthetic case-objects should be initialized early. #2458
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.
Lazy val implements non-static objects.
But if object is not user-defined we don't make it
real
lazy,we instead make it eager as no-one will notice. This actually
saves resources as otherwise you'll still need to initialize
lazy-val related stuff in constructor instead and later initialize
actual objects.
Those objests, being eager, should be initialized early,
so that constructors can't see un-initialized values.