Jiaxiang
03/11/2021, 12:51 AMfindAnnotationFromUseSiteTarget()
function, consolidate its functionality into KSP internal logic.
Behavior change
• KSP now handles annotation use site targets internally for property accessors (namely @get:Anno
, @set:Anno
).
◦ property accessors will have corresponding targeted annotations from their receiver properties
◦ annotations with @get:
and @set:
targets will not appear in property’s annotation list.Javier
03/11/2021, 12:59 AMJiaxiang
03/11/2021, 1:12 AMJavier
03/11/2021, 1:26 AMTing-Yuan Huang
03/11/2021, 8:52 AMkotlin("multiplatform")
+ kotlin { jvm() }
) will be usable in next bi-weekly release. JS and Kotlin native require some changes in upstream compiler that we are currently working on. They won't be available in Kotlin 1.5.0 since it already branched.Javier
03/11/2021, 11:49 AMMiguel Vera Belmonte
03/11/2021, 9:29 PMkspKotlinJs
task generated the sources in the same folder as the kspKotlinJvm
task, and thus JVM and JS sources were being compiled in the same sourceset, but that could be relatively easily fixed by changing the folder depending on the target platform in KSP, right? Is that it or is there another issue with the Kotlin compiler altogether?
Just asking so that I can get a grasp of the inner workings of the library and the compiler 😁Ting-Yuan Huang
03/11/2021, 10:11 PMAnalysisHandlerExtension
) for KSP to hook on.
For pure Kotlin sources that only uses the common set of Kotlin features, it might be possible to use kotlin/jvm to generate for other platforms by manipulating source sets carefully. I haven't tried that way but I guess it could be tricky.Miguel Vera Belmonte
03/12/2021, 9:28 AM