val kiraAnn = getAnnotationsByType(Kira::class).first()
kiraAnn.customization
I get the following error:
e: [ksp] java.util.NoSuchElementException: Collection is empty.
at kotlin.collections.CollectionsKt___CollectionsKt.single(_Collections.kt:592)
at com.google.devtools.ksp.symbol.impl.binary.KSAnnotationDescriptorImplKt.createKSValueArguments(KSAnnotationDescriptorImpl.kt:151)
at com.google.devtools.ksp.symbol.impl.binary.KSAnnotationDescriptorImpl$arguments$2.invoke(KSAnnotationDescriptorImpl.kt:88)
at com.google.devtools.ksp.symbol.impl.binary.KSAnnotationDescriptorImpl$arguments$2.invoke(KSAnnotationDescriptorImpl.kt:87)
at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
at com.google.devtools.ksp.symbol.impl.binary.KSAnnotationDescriptorImpl.getArguments(KSAnnotationDescriptorImpl.kt:87)
at com.google.devtools.ksp.UtilsKt.createInvocationHandler(utils.kt:350)
at com.google.devtools.ksp.UtilsKt.asAnnotation(utils.kt:427)
at com.google.devtools.ksp.UtilsKt.access$asAnnotation(utils.kt:1)
at com.google.devtools.ksp.UtilsKt$createInvocationHandler$1$value$3.invoke(utils.kt:375)
at com.google.devtools.ksp.UtilsKt.createInvocationHandler$lambda-8(utils.kt:546)
at com.sun.proxy.$Proxy33.customization(Unknown Source)
at com.popovanton0.kira.processing.KiraProcessor.getKiraAnn(KiraProcessor.kt:348)
at com.popovanton0.kira.processing.KiraProcessor.process(KiraProcessor.kt:20)
............
error does not occur. Seems like a bug. Similar to #784?
ksp version = 1.6.21-1.0.5
kotlin version = 1.6.21
I created a branch in my repo that reproduces this behaviour. To reproduce, run this unit test. Input to the test is here. Code of the processor is here.
The text was updated successfully, but these errors were encountered:
When analyzing a function
annotated with this annotation:
and executing this code in the symbol processor:
I get the following error:
However, with this annotation:
error does not occur. Seems like a bug. Similar to #784?
ksp version =
1.6.21-1.0.5
kotlin version =
1.6.21
I created a branch in my repo that reproduces this behaviour. To reproduce, run this unit test. Input to the test is here. Code of the processor is here.
The text was updated successfully, but these errors were encountered: