Introduction

In the realm of Kotlin, a kingdom of powerful constructs awaits developers, ready to be harnessed for diverse scenarios. Among these regal constructs are sealed classes and enums, adorned with their own unique characteristics and purposes. In this splendid blog post, we embark on a journey to explore the lavish differences between sealed classes and enums in Kotlin. Through resplendent code snippets and illustrious examples, we shall unravel their splendorous usage and applications.

Section 1: Introduction to Sealed Classes and Enums

Before we immerse ourselves in the opulent distinctions between sealed classes and enums, let us acquaint ourselves with these majestic constructs.

Sealed Classes:

Behold, the sealed class, a noble entity that bestows restrictions upon its subclasses. With its powers, it confines the realm of subclasses within the same file or module. Sealed classes are often favored when the need arises to acknowledge and handle a finite number of subclasses, ensuring that all possibilities are known and gracefully embraced.

Enums:

Welcome, dear reader, to the realm of enums, where a fixed set of constant values reign supreme. In Kotlin, enums manifest as regal classes, adorned with a limited number of predefined instances. Their majestic presence graces us when we require a small, fixed set of options that stand alone in their exclusive nature.

Section 2: Distinctions between Sealed Classes and Enums

2.1 Extensibility:

One of the key differentiating factors between sealed classes and enums lies within their extensibility. The sealed class, ever open to the wonders of extension, allows the creation of new subclasses within the same file or module. On the contrary, the enum, a bastion of exclusivity, remains closed to extension, disallowing the creation of new instances or subclasses.

sealed class Result
class Success(val data: Any) : Result()
class Error(val message: String) : Result()

enum class Status {
    SUCCESS, ERROR
}

2.2 Usage in When Expressions:

Both sealed classes and enums hold the potential to grace the exalted halls of “when” expressions, yet their behavior diverges subtly. When employing a sealed class within a “when” expression, one must gracefully handle all possible subclasses, ensuring a symphony of coverage and preventing any discordant compilation errors.

fun processResult(result: Result) {
    when (result) {
        is Success -> {
            // Revel in the triumphant success!
        }
        is Error -> {
            // Alas, an error has befallen us!
        }
    }
}

In contrast, enums shimmer within “when” expressions without the need for explicit handling of all cases. The compiler, ever vigilant, checks if all enum values are embraced, graciously gracing us with a compilation error should any cases be overlooked.

fun processStatus(status: Status) {
    when (status) {
        Status.SUCCESS -> {
            // Bask in the glory of success!
        }
        Status.ERROR -> {
            // Face the challenges presented by an error!
        }
    }
}

2.3 Flexibility in Data Structures:

Sealed classes, dear reader, offer a realm of unbridled flexibility when it comes to defining the structure of data associated with each subclass. Each subclass, a unique entity in its own right, boasts its properties, methods, and distinctive behavior. This opulence allows for the creation of intricate data structures, where each subclass is treated with the reverence it deserves.

On the other hand, enums possess a fixed structure, shared amongst all instances. While each enum instance may possess additional properties and methods, these treasures are shared amongst all individuals within the enum class.

sealed class Vehicle {
    abstract fun drive()
}

class Car(val model: String) : Vehicle() {
    override fun drive() {
        println("Driving the esteemed car $model")
    }
}

class Bike(val brand: String) : Vehicle() {
    override fun drive() {
        println("Embarking on a grand adventure with the majestic bike $brand")
    }
}

enum class Color(val rgb: Int) {
    RED(0xFF0000),
    GREEN(0x00FF00),
    BLUE(0x0000FF)
}

2.4 Memory Usage:

Behold, for enums, crafted as singletons, exude an aura of exclusivity. Within their realm, only one instance of each enum value exists, ensuring a realm of efficiency in memory usage. This luxury becomes evident in scenarios where a fixed set of options reign supreme, gracefully shared amongst all who traverse their dominion.

Sealed classes, however, offer a more diverse array of instances within each subclass. This grandeur, while resplendent, may result in increased memory usage when numerous instances grace the realm or when instances dynamically emerge at runtime.

2.5 Opulent Use Cases:

Sealed classes, dear reader, often find their place in the grand tapestry of code when a realm of closed, interrelated classes requires expression. They shine with a radiant brilliance when tasked with modeling state machines, where each sealed class represents a distinct state, a jewel in the crown of architectural elegance.

Enums, on the other hand, grace our code with their elegance when a small, distinguished set of options demands representation. They are cherished companions in the realm of categories, status codes, or any other scenario where a limited number of choices reign supreme.

Section 3: Conclusion

Sealed classes and enums, both resplendent constructs within the kingdom of Kotlin, possess their own unique strengths and purposes. Sealed classes, with their extensibility and flexibility in data structures, offer a realm of boundless possibilities for modeling intricate hierarchies. Enums, on the other hand, exude an aura of exclusivity, providing a fixed set of options, coupled with memory efficiency, in the pursuit of representing mutually exclusive choices.

To wield the power of sealed classes and enums with finesse, understanding their distinctions is paramount. By embracing the splendor of these constructs, you shall grace your codebase with elegance, fostering an environment of maintainable and luxurious Kotlin code.

Reference

Original Blog Post