You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
KSP1 (test pass) can correctly name its getter/setter as getIsoSomething/setIsoSomething, which match kotlin compiler behavior too
KSP2 (test fail) will incorrectly name its getter/setter as isoSomething/setoSomething
Personal understanding
My personal understanding is that KSP1 resolver and kotlin compiler use JvmAbi.startsWithIsPrefix, but ksp2 just develop the logic by itself, and missed the condition that check whether the letter after is is capitalized
Repro
acejingbo@92b37b9
Notice for property like
isoSomething
.getIsoSomething
/setIsoSomething
, which match kotlin compiler behavior tooisoSomething
/setoSomething
Personal understanding
My personal understanding is that KSP1 resolver and kotlin compiler use JvmAbi.startsWithIsPrefix, but ksp2 just develop the logic by itself, and missed the condition that check whether the letter after
is
is capitalizedhttps://github.com/JetBrains/kotlin/blob/master/core/compiler.common.jvm/src/org/jetbrains/kotlin/load/java/JvmAbi.kt#L88-L94
The text was updated successfully, but these errors were encountered: