0a3e8fbe66
- DeserializedPackageFragmentImpl doesn't actually need member scope to be lazy in a sense of optimization. It was only necessary for breaking initialization cycle: DeserializationComponents <-> DeserializedPackageFragment - For MetadataPackageFragment it might be useful to have member scope actually lazy since it has O(n) complexity when n is a number of package parts This change is helpful for avoidance of storing reference to package-proto #KT-24513 In Progress