The JVM and the Kotlin compiler

What actually happens when `kotlinc` compiles your code: bytecode, class files, memory management and garbage collection on the JVM, the compiler pipeline from lexer to codegen, the modern K2 compiler, and what data classes or inline functions really trigger in the bytecode. For anyone who has finished "Kotlin Introduction" and "Object-Oriented Programming" and wants to understand what runs under the hood.

0 / 8 completed

Module 1 · The JVM as a foundation
011. From Kotlin code to the JVMLESSON
—2. Memory and garbage collectionLOCKED
Module 2 · The Kotlin compiler from the inside
—3. Frontend and backend: The compiler pipelineLOCKED
—4. What the frontend really checks: Analyses and smart castsLOCKED
—5. K2: The modern Kotlin compilerLOCKED
Module 3 · Bytecode & interop in practice
—6. Reading bytecode: Decompilers and Kotlin idiomsLOCKED
—7. Java interop: Platform typesLOCKED
—8. Inline functions: Performance at the bytecode levelLOCKED
8 lessonsModule 1 · The JVM as a foundationModule 2 · The Kotlin compiler from the insideModule 3 · Bytecode & interop in practiceProgress: local, no account required