kotlin-expert

State management in Kotlin Multiplatform uses StateFlow for state ownership and SharedFlow for event broadcasting. StateFlow holds a single mutable state value, while SharedFlow emits values to multiple collectors without retaining state.

Sealed classes and interfaces in Kotlin provide restricted hierarchies for type-safe state representation and error handling. They allow exhaustive when expressions, ensuring all possible subtypes are handled at compile time.

Inline functions and reified generics optimize Kotlin performance by eliminating runtime type erasure overhead and removing lambda allocation costs. The compiler substitutes the function body directly at the call site, preserving generic type information.

Use @Immutable with data classes in Kotlin Multiplatform when ensuring data integrity and optimizing Compose performance. It marks classes where all properties are immutable, allowing the Compose compiler to skip recomposition for unmodified inputs.

Building a type-safe DSL in Kotlin involves using DSL builders and function literals with receiver to create expressive APIs. This pattern allows you to define hierarchical structures with compile-time validation and fluent syntax.

Common Kotlin anti-patterns for state management include overusing SharedFlow for state retention instead of StateFlow, and creating unnecessary object allocations. Decision trees help choose appropriate constructs to avoid these performance bottlenecks.