Explain lateinit var versus val by lazy in Android
Tests deferred initialization and lifecycle coupling. Great answers contrast lateinit var's imperative assignment with lazy's first-access delegation, mapping lateinit to injected Activity fields and lazy to expensive computed objects.
Tests deferred initialization trade-offs and Android lifecycle mapping. A strong answer separates lateinit var, which needs imperative assignment after declaration and only works with non-nullable non-primitive mutable properties, from val by lazy, which delegates initialization to first access and yields an immutable reference. Then it maps lateinit to dependency injection or view binding set in onCreate, and maps lazy to expensive object creation that may never be accessed.
Read the original → kotlinlang.org
- #kotlin
- #android
- #property-delegation
- #lateinit
- #lazy
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.