Implement Jdeps using K2 APIs #1166
Open
+621
−30
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.
This PR adds support for running Jdeps when compiling with K2 (#843).
High level list of changes:
JdepsGenExtension2
which leveragesFirAdditionalCheckers
plugin extension to collect info from the FIR treeClassUsageRecorder
object to manage collection of AST infoClassUsageRecorder
is init in the registrar & dumped to a proto on theClassFileFactoryFinalizerExtension
callback since there is no longer aonAnalysisCompleted
callback in K2FirClassSymbol
,FirTypeRef
, &ConeKotlinType
which is then pushed into theClassUsageRecorder
so that supertypes & type args can also be collected, if necessaryJdepsGenComponentRegistrar
to invoke K1 or K2 impl based on language version set in the kotlinc configurationNote to reviewers: Tests on CI will likely fail until the Kotlin JS std lib for 2.0 issue is properly sorted out