Community
Participate
Working Groups
Build 3.0m1 (also reported in 2.0 stream) Some client reported that compilation would take a long time in presence of large units with numerous single type imports. A code examination reveals that we could use a cache technique to avoid iterating them all when resolving subsequent type references. Would need to be backported in 2.0 & 2.1 maintenance streams.
Brian: We need to a 'real' PR to be able to backport this to 2.0.x.
Backported to 2.1.1 maintenance stream. Brian: Please connect this PR with whatever one in the other system started the process.
Verified.
Candidate for 2.1.2
Created attachment 6468 [details] Not really smart but efficient test case A real simple class with 182 imports.
Verified with build 2.1.2 RC1
Verified with build 2.1.2 RC2 that single type imports are cached in CompilationUnitScope.resolvedSingleTypeImports