Pure Kotlin.
summary
Argues Kotlin supports real functional code: immutable data models with data class copy for cheap persistent updates, prefer Val not var and expression-style functions to force totality, and wrap side effects in IO-like monads so actions are explicit. Recommends using Vavr or Kotlin immutable collections instead of java.util, points to Arrow/Arrow FX for effects and mentions a Detekt plugin (curopotamin) to statically enforce purity rules. Shows how these choices catch bugs (e.g., missed states, double side effects) before runtime.
AI-written summary · about
chapters (10)
- 0:00Introduction to talk
- 1:53Why functional programming matters
- 6:11Mathematical functions in Kotlin
- 13:15Kotlin's killer features
- 21:52Immutability and data structures
- 27:15Expressions over instructions
- 34:21Managing side effects
- 41:04Functional programming in production
- 46:00Tools for purity in Kotlin
- 48:29Q&A and closing
related talks
44mKotlin & Functional Programming: pick the best, skip the rest
48mKotlin & Functional Programming: pick the best, skip the rest
50mState of the functional ecosystem in Kotlin: Mid 2018 checkup
27mWhy Kotlin is my favourite example of Functional Programming?
30mWhat can Kotlin do for me?
39mKotlin for the Pragmatic Functionalist
49mImperative, declarative, object oriented, functional: four of a Kotlin kind
50mKotlin is as awesome as you've heard. Here's why.