f5d2ce3022
AA: render containing file and JvmClassName
2023-12-21 15:34:34 +00:00
23363ef1bd
KT-61728 [LL API] Use ContextCollector in AllCandidatesResolver
...
Fix testdata for builder inference test in resolve tests - now it's the
same between K1 and K2
2023-09-08 14:41:39 +00:00
72d8fa216a
[AA] DebugSymbolRenderer: move annotations and type arguments renderer befor type to avoid resolve race
...
^KT-56046
2023-02-03 19:48:56 +00:00
1e2d517c21
[AA] DebugSymbolRenderer: improve type render
...
to process all nested annotations and types
^KT-56046
2023-02-03 19:48:55 +00:00
37d688ae83
[AA] introduce FirReceiverParameter
...
^KT-54417
2022-11-17 09:50:09 +00:00
66851c7afd
[Analysis API] Add KtReceiverParameterSymbol#correspondingSymbol
2022-06-27 19:32:44 +00:00
2234813363
[Analysis API] Add KtCallableMemberCall#typeArgumentsMapping
2022-06-23 07:50:21 +00:00
8d8fc6e291
[Analysis API] Add type to KtReceiverValue
...
Maybe in the future we could remove type from the
KtImplicitReceiverValue, because it has ktSymbol, and in theory
that should be enough to create corresponding KtType.
Unfortunately that is not the case for KtClassOrObjectSymbol --
it doesn't have the API for "default" type creation currently.
Regarding code in KtFirCallResolver.kt -- it seems like code there
needs some love in the future. Psi created via custom code there,
because for call x() FIR has receiver x with psi = null
2022-06-23 07:50:21 +00:00
2c1074ac37
[Analysis API] actualize testdata
2022-06-22 09:31:45 +02:00
3f3873dc50
Analysis API: Return KtCallCandidateInfo instead of KtCallInfo in
...
KtCallResolver.collectAllCandidates().
2022-02-11 13:22:58 +01:00
58c6c25fe9
Analysis API: Handle other FirElements in
...
KtCallResolver.resolveCandidates() and copy over remaining tests.
2022-02-11 13:22:58 +01:00
Jinseong Jeon