Skip to main content

Blog: Zero-Cost Types - Inline Value Classes in Kotlin

Blog: Zero-Cost Types - Inline Value Classes in Kotlin

Day 53! Today I dove deep into Inline Value Classes in Kotlin. In professional software architecture, a common design goal is achieving Type Safety. For instance, instead of passing around raw, generic strings for database keys, passwords, or security hashes, you want to wrap them inside dedicated domain types like SecureIdToken.

This prevents catastrophic mistakes where a developer accidentally passes a standard username string into a sensitive security token slot.

The Performance Penalty of Wrappers

While wrapping primitives is an architectural win, it comes with a major catch on the JVM: Object Allocation Overhead.

Creating thousands of tiny wrapper objects forces the runtime environment to constantly allocate heap memory, causing visual lag, slow operations, and heavy garbage collector pressure in data-intensive apps.

The Secret Trick: @JvmInline value class

Kotlin solves this performance dilemma completely using Inline Value Classes. By combining the value class keyword with a @JvmInline decorator, you instruct the compiler to perform a clever optimization trick:

@JvmInline
value class SecureIdToken(val idString: String)

At compile time, the compiler completely flattens the wrapper. In the resulting compiled bytecode, the wrapper class instance object is entirely deleted, leaving behind only the raw underlying primitive string itself!

High-Level Features for Free

Even though it compiles down to a raw primitive under the hood, you can write value classes exactly like real classes: - You can add init blocks to validate inputs instantly upon creation. - You can define custom computed properties and formatting getters (maskedToken). - You can declare member methods and domain functions natively.

During compilation, these class methods are transformed into optimized static methods that process the raw primitive parameter directly. You get the beauty and security of strongly typed domain objects, with the hyper-fast performance of raw primitives!

Summary

Inline value classes allow developers to create type-safe architectures with zero object allocation overhead, successfully removing the friction between performant execution and clean design.

Check out the full technical breakdown!

Kotlin #ValueClasses #JvmInline #Optimization #CleanCode #AndroidDev #JVM #ProgrammingJourney

Comments

Popular posts from this blog

Mastering Per-App Language Preferences: From Android 10 to Android 13+

  One of the most requested features by users is the ability to use an app in a language different from the system language. While Android 13 (API 33) introduced "Per-App Language" settings at the system level, implementing this backward-compatibly for older devices like Android 10 (API 29) used to be a challenge involving manual configuration wrapping. Today, thanks to AppCompat 1.6.0+ , we have a unified, standard way to handle this. Here is the modern guide to implementing seamless language switching. The Architecture: How it Works On Android 13 and above, the system handles the storage and application of your app's locale. On older versions, the AppCompat library manages this behavior by storing your preference in an internal XML file and injecting the resources during the activity lifecycle. Step 1: The Locale Helper Utility Instead of scattering logic across your app, use a clean LocaleHelper object. This handles the distinction between the system LocaleManager (...

Beyond Scanning: Meet the All-in-One AI Document Assistant by Digitify Vision Technology

In an era where efficiency is the ultimate currency, information is scattered everywhere—on physical paper, within QR codes, and inside lengthy digital documents. The challenge isn't just capturing this data; it’s making it work for you. At Digitify Vision Technology , we believe your smartphone should be more than just a camera—it should be a high-performance engine for your daily workflow. Today, we are proud to unveil our most powerful update yet: a total evolution in AI-driven document management. 💡 Key Features of the New Update We’ve bridged the gap between physical information and digital action by integrating advanced vision and audio intelligence into a single, seamless experience. 🔍 Precision Scanning for Everything Our advanced vision engine is now more versatile than ever. Intelligent Document Scanning: Capture crisp, professional-grade scans of physical papers, contracts, or handwritten notes. QR Code Extraction: Instantly scan any QR code to extract text, read URL...
  Optimising Android Launch: Mastering App Startup & The Modern Splash Screen The first few seconds of an app’s life determine a user's first impression. A slow start or a flickering white screen can lead to immediate uninstalls. In this guide, we’ll look at how to streamline your initialisation using the App Startup Library and ensure a seamless visual transition with the Android 12 Splash Screen API (with full backward compatibility for API 29). Part 1: The App Startup Library Traditionally, apps initialised multiple components using separate content providers. This adds overhead and slows down launch time. The Jetpack App Startup library allows all components to share a single content provider, significantly improving performance. Why use it? Performance: Shared content provider reduces overhead. Order: Explicitly set the initialisation sequence. Simplicity: Both library creators and app developers use a unified interface. Part 2: The Modern Splash Screen API Starting ...