K2 Compiler plugins
summary
Lists K2 changes versus K1 with concrete effects: K2 plugin API exposes explicit extension points, predicates, and transforms so plugins can add members, change modifiers, register new diagnostics, or extend type checks; it distinguishes front-end vs back-end plugins (front-end can affect analysis and diagnostics, back-end edits IR but cannot change earlier analysis), shows migration pitfalls and Gradle/IDE wiring, compares KSP and annotation processors, gives examples (no‑arg, all‑open, serialization, reflect, Compose) and reports that K2 improves IDE support and performance though API stabilization is ongoing.
AI-written summary · about
chapters (24)
- 0:00Intro
- 2:52No source code generation!
- 3:13Make classes & members open
- 4:13Improve your DSL
- 6:11Standard compiler plugins
- 6:55Extend type system
- 8:20Black box compiler level
- 8:58Frontend-backend compiler level
- 9:37K2 Frontend structure
- 12:15Approaches to extending compiler
- 13:19Kotlin Annotation Processing (KAPT)
- 15:10Kotlin Symbol Processing (KSP)
- 17:48Kotlin Compiler plugins
- 20:21Backend VS Frontend plugins
- 23:06Backend plugins
- 23:30IR backend plugin: API
- 25:38Frontend compiler plugins
- 26:39Frontend: kotlinx.serialization
- 30:18K2 plugin API. Capabilities
- 31:27K2 plugin API. Extension example
- 33:51K2 plugin API. Other predicates
- 34:37K2 frontend plugin creation
- 35:48K1 plugin usage (Gradle)
- 36:39K2 plugin usage PLANNED DSL
related talks
42mMeta-programming with K2 compiler plugins
35mK2 compiler in production
33mMeta-programming with KSP and Kotlin compiler plugins
01h 13mThe Magic of Kotlin Compiler Extensions
36mMeta-programming with Kotlin compiler plugins
38mKSP and Plugins. Optimizing Kotlin Multiplatform common code
45mCompiler plugins: modifying and analyzing Compose
26mUpgrading Meta's Kotlin Infrastructure to K2