I'm just whining. I've been waiting months until K...
# random
r
I'm just whining. I've been waiting months until KSP was no longer a compiler plugin to easily test new Kotlin versions. Just to realize my project is now bound to Koin compiler plugin and it don't work with Kotlin 2.4.0-Beta ;(
e
Yeah that's why I tend to minimize compiler plugins, although at some point, some are inevitable and you're locked in.
➕ 1
t
we are working on it: KT-82617 DevKit for Kotlin compiler plugins
gratitude thank you 1
o
Very much looking forward to the compiler plugin DevKit! Apart from that, yes: If we need to operate on the latest Kotlin versions, our dependencies with compiler plugins better be leading-edge, too – or rather bleeding edge. Metro has been pretty good at that task, also TestBalloon users have never missed an EAP cycle so far.
c
Yeah that's why I tend to minimize compiler plugins
Same. The only non-bundled compiler plugin I use is TestBalloon, because so far it has never slowed me down. All others I have end up removing.
o
If the latest compiler releases are indicative, the situation might improve, as migrating to new compiler versions requires less and less effort. Of course, compiler plugin maintainers have to care. Same with IDE plugins.