Heads up: Kotlin compiler plugins compiled with Kotlin 1.3 can’t be used in projects using Kotlin 1....

# compiler

[ralf]

Heads up: Kotlin compiler plugins compiled with Kotlin 1.3 can’t be used in projects using Kotlin 1.4 M3 (M2 is fine). I filed a ticket and added a sample to reproduce the issue: https://youtrack.jetbrains.com/issue/KT-40214

[turansky]

It’s expected breaking change as I understand.
1.4 has updated/changed plugin API.

[ralf]

I don’t see a breaking change in my plugin. But yes, seems to be the case.

[turansky]

[turansky]

https://blog.jetbrains.com/kotlin/2020/07/kotlin-1-4-m3-is-out-standard-library-changes/

[jw]

Compiler plugins basically always break with new releases. They have no stability guarantees.

[ralf]

@turansky I saw that and double checked: https://youtrack.jetbrains.com/issues/KT?q=Tag:%20language-committee-approved%20Target%20versions:%201.4-M3,%201.4-M2,%201.4-M1,%201.4.0&_ga=2.225808282.1002681388.1594512680-919897319.1560536387

It make sense and I assume that’s also the reason they publish a new preview build for the serialization library. A word about compiler plugins in the compatibility section wouldn’t hurt.

[turansky]

Common problem - 1.3 binaries + 1.4 binaries = undefined behaviuor

In my cases String.replace and Collection.add don’t work as expected