fix scala 2.11 having problems finding default values of nested case classes because of uninitialized type metadata #51
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.
Configs with scala 2.11 has problems finding default values of nested case classes. I had the following cases:
The strange thing about these errors is that they are not reproducible in unit tests of this project. I guess that it has to do with the numbers of macros that are generated in the project, and that scala optimizes loading of corresponding type metadata.
With this fix we can force scala to initialize type metadata before reading default values from it. This solves above cases.