kotlin-patterns

Topics in the source

• Kotlin Development Patterns
• When to Use
• How It Works
• Examples
• Core Principles
• 1. Null Safety
• 2. Immutability by Default
• 3. Expression Bodies and Single-Expression Functions

Idiomatic Kotlin patterns and best practices for building robust, efficient, and maintainable applications. Writing new Kotlin code Reviewing Kotlin code Refactoring existing Kotlin code Designing Kotlin modules or libraries Configuring Gradle Kotlin DSL builds This skill enforces idiomatic Kotlin conventions across seven key areas: null safety using the type system and safe-call operators, immutability via val and copy() on data classes, sealed classes and interfaces for exhaustive type hierarchies, structured concurrency with coroutines and Flow, extension functions for adding behaviour without inheritance, type-safe DSL builders using @DslMarker and lambda receivers, and Gradle Kotlin DSL for build configuration. Null safety with Elvis operator: Sealed class for exhaustive results: Structured concurrency with async/await: Kotlin's type system distinguishes nullable and non-nullable types. Leverage it fully. Prefer val over var, immutable collections over mutable ones. Use expression bodies for concise, readable functions. Use data classes for types that primarily hold data. | Idiom | Description | |-------|-------------| | val over var | Prefer immutable variables | | data class

This is an excerpt. Refer to the complete source and its current requirements.