kotlin-types-value-class

Prefer a Kotlin value class for single-field domain types to ensure type safety while avoiding unnecessary allocations at runtime. Use data classes only when multiple fields are required.

Kotlin value classes support Compose stability by providing zero-runtime allocation for single-field types, ensuring efficient recompositions. This Skill documents their compatibility and stability implications within Compose.

Use a Kotlin value class for true type safety at runtime without allocation overhead, whereas a type alias merely provides a compile-time name without distinct type boundaries. The Skill guides choosing between them.

Limitations of @JvmInline value classes include supporting only a single field and potential Java interoperability constraints. The Skill outlines when to avoid them in favor of data classes or type aliases.

To replace a single-field data class, apply the @JvmInline annotation and implement the value class interface. This transition eliminates unnecessary object allocations while maintaining type safety.

Kotlin value classes have specific Java interoperability considerations due to their underlying inline representation. The Skill documents these compatibility details to ensure seamless cross-language usage.