You Can, but Should You?
summary
Why use one Kotlin feature over another: shows concrete pitfalls like shadow variables in nested lambdas, opportunistic extension functions that leak project-specific behaviour into String or Context, and top-level helpers that pollute autocomplete; demonstrates decompiling generated JVM bytecode to compare for/indices vs forEach performance and allocation differences; warns about over-eager type inference and one-line functions changing return semantics; recommends coding guidelines, periodic refactors, benchmarks and documenting deliberate choices so teams can decide what they can do and should do.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 4:25The 5 Stages
- 10:35Potential Problems
- 16:30Shadow Variables
- 20:34opportunistic extension functions
- 25:44opportunistic toplevel functions
- 31:04from other languages
- 33:37oneliner functions
