ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Kotlin sealed classes and interfaces model finite domain states with compiler-checked exhaustive when expressions. Covers syntax, serialization, sealed interfaces for multiple inheritance, and production trade-offs: binary compatibility, DEX count, R8 stripping.
Dart 3 sealed classes replace null-sentinel returns and forgotten error branches with compiler-checked domain models. A worked example shows exhaustive switching over a profile-fetch result type.
Nullable data/error field pairs silently break when a new state is added. Kotlin sealed interfaces make the set of states closed, so the compiler flags every when that misses a case.
Kotlin’s sealed classes let you model API responses as a closed hierarchy, ensuring exhaustive handling at compile time. Learn how to define a Result type, use exhaustive when, and understand the trade‑offs in this practical guide.
When UI logic grows, managing state with flags can lead to illegal combos and bugs. Sealed classes give compile‑time exhaustiveness, making state machines safer and easier to extend. This guide shows how to model UI states, why it works, and the trade‑offs.
Learn when to use Kotlin data classes versus sealed classes for state management. This guide compares product types and sum types to help you build type-safe application architectures.
Groovy 4 vs Java 17 sealed classes: can Groovy extend a sealed Java class? The goal is to determine whether Groovy 4 can legally extend a sealed Java 17 class or interface, and if so, how the compiler and runtime enforce the sealed hierarchy. Current observations indicate that Groovy 4’s compiler accepts subclasses of sealed Java types that are not listed in
kotlin
flutter