Flexible Types in Kotlin
summary
Kotlin adds platform types to bridge JVM interop, treating Java types as a pair of narrow/wide bounds so the compiler lets risky calls compile and defers failure to runtime; that design intentionally sacrifices type-soundness to avoid JVM-call overhead. Arrays get runtime checks like Java, but generic collections introduce a real regression — Kotlin can be less safe than Java because covariant read-only views plus erasure let a List<String> flow into a List<Object> and fail later. Annotations and extra runtime guards reduce but don’t eliminate these problems; the same machinery also enables a JavaScript dynamic mode.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:25Safety Features
- 2:30Interoperability
- 3:12Example: Arrays
- 5:51Java (as seen from Kotlin)
- 6:54Java Interop: All Nullable
- 8:36Annotations
- 10:31Pick Two
- 11:33Dereferencing Flexible Values
- 12:11Assignability
- 14:44Representation
- 16:24Equivalence
- 18:03Runtime Checks (and their absence)
- 19:34Some Notes
- 21:03Kotlin Arrays
- 23:00Arrays: Example
- 25:24Java: Flexible Types
- 31:54Ad Hoc Check
- 32:41Runtime Checks and their absence
- 34:23Raw Types
- 37:14Summary (11)
- 40:23Expressing dynamic types for
