Kotlin 2.4 Ships with Java 26 Support and Stable Context Parameters

By Vatsal Shah | 2026-07-31 | 6 min read

Table of Contents

1. Introduction
2. What Shipped as Stable
3. Context Parameters: From Experimental to Production-Ready
4. Explicit Backing Fields
5. Java 26 JVM Support
6. Kotlin/Wasm: Incremental Compilation and Component Model
7. Experimental: Collection Literals
8. Kotlin/Native: Swift Package Import and Swift Export Alpha
9. Gradle and Build Tooling
10. Why This Release Matters for Enterprise Teams
11. FAQ
12. About the Author
13. Conclusion

Introduction

JetBrains has shipped Kotlin 2.4.0, the first major Kotlin release of Q3 2026. While incrementally numbered, this release punches well above its version bump. Four language features that spent multiple releases in experimental status — most notably context parameters and explicit backing fields — have now graduated to Stable. For Android, backend, and multiplatform teams, this is the green light to adopt them in production code without opt-in pragma overhead.

Beyond language stabilizations, Kotlin 2.4.0 formalizes Java 26 JVM target support, enables incremental compilation on Kotlin/Wasm by default, and begins shipping experimental WebAssembly Component Model integration — a capability that opens Kotlin/Wasm to the rapidly growing component-interop ecosystem.

![Kotlin 2.4 Feature Map](/uploads/content/news/kotlin-2-4-java-26-context-parameters-2026/kotlin-24-features-map.webp "Kotlin 2.4 New Features Map")

What Shipped as Stable

Kotlin 2.4.0 promotes the following features from Experimental/Preview to Stable status, meaning no opt-in annotation required:

• Context parameters (excluding context arguments and callable references — those remain experimental)
• @all meta-target for properties
• New defaulting rules for use-site annotation targets
• Explicit backing fields
• UUID API in the common standard library
• New API for converting unsigned integers to BigInteger on JVM
• Sorted order checking support (isSorted, isSortedBy)
• Value class export to JavaScript/TypeScript
• ES2015 features in JS code inlining
• Maven: automatic Java/JVM target version alignment
• Maven Toolchains support

This represents the largest single-release stabilization batch in Kotlin's recent history.

Context Parameters: From Experimental to Production-Ready

Context parameters are Kotlin's answer to implicit parameter threading — a clean, compiler-enforced mechanism to pass ambient dependencies (like loggers, transaction contexts, or security principals) to functions without cluttering every call site.

// Function requiring a Logger context
context(logger: Logger)
fun performOperation() {
    logger.info("Operation started")
    // ... logic
}

// Calling function provides context automatically
context(appLogger: Logger)
fun processRequest() {
    performOperation()   // Logger injected implicitly
}

With 2.4.0, this syntax is Stable. Teams no longer need @OptIn(ExperimentalContextParameters::class) in every file. The feature is particularly valuable for:

• Dependency injection without DI frameworks: Pass repositories, loggers, and transaction managers implicitly.
• DSL builders: Create cleaner, more composable builder scopes.
• Structured concurrency contexts: Pass coroutine scopes and dispatchers contextually.

Also newly experimental in 2.4.0: Explicit context arguments at call sites, which resolve ambiguity when multiple overloads differ only by context parameter type:

context(emailSender: EmailSender)
fun sendNotification() { println("Email sent") }

context(smsSender: SmsSender)
fun sendNotification() { println("SMS sent") }

context(email: EmailSender, sms: SmsSender)
fun notifyUser() {
    sendNotification(emailSender = email)  // Disambiguates explicitly
    sendNotification(smsSender = sms)
}

Enable with compiler flag: -Xexplicit-context-arguments.

Explicit Backing Fields

Kotlin 2.4.0 also stabilizes explicit backing fields, allowing you to declare val field: T directly inside a property definition. This eliminates common by lazy or private backing property boilerplate for complex property semantics:

class DataCache {
    val items: List<String>
        field = mutableListOf()         // Explicit backing field
        get() = field.toList()          // Computed getter over backing field
}

Previously this pattern required a private mutable backing property plus a public read-only property — two declarations. Explicit backing fields collapse it to one.

Java 26 JVM Support

![Kotlin 2.4 Context Parameters Diagram](/uploads/content/news/kotlin-2-4-java-26-context-parameters-2026/kotlin-context-parameters-diagram.webp "Kotlin Context Parameters before and after 2.4")

Kotlin 2.4.0 adds official support for Java 26 as a JVM target and compilation target. This is significant for teams:

• Already running Java 26 LTS preview runtimes or early-adopter environments.
• Using Java 26's Project Valhalla value types (when finalized) or primitive classes in mixed Kotlin-Java codebases.
• Building server-side Kotlin applications requiring the latest JDK for security patches.

Additionally, annotations in metadata are now enabled by default, improving tooling compatibility with Kotlin metadata consumers (reflection libraries, compile-time processors).

Kotlin/Wasm: Incremental Compilation and Component Model

Two major Wasm improvements ship in this release:

1. Incremental compilation enabled by default: Kotlin/Wasm modules now compile incrementally, dramatically reducing build times for large multiplatform projects targeting Wasm.
2. WebAssembly Component Model support (Experimental): The Component Model is the standardization layer for composable, language-agnostic Wasm modules. Kotlin/Wasm can now interop with components built in other languages (Rust, C, Go) through the standard Component Model interface, unlocking a new class of polyglot Wasm applications.

Experimental: Collection Literals

Kotlin 2.4.0 ships experimental support for collection literals using bracket syntax:

// Before 2.4.0
val shapes = listOf("triangle", "square", "circle")
val mutable: MutableList<String> = mutableListOf("a", "b")

// Kotlin 2.4.0 collection literals
val shapes = ["triangle", "square", "circle"]           // Inferred as List<String>
val mutable: MutableList<String> = ["a", "b"]           // Inferred as MutableList

The compiler infers collection type from the declared type context. Custom operator fun of functions can extend bracket syntax to user-defined collection types. Enable with -Xcollection-literals.

Kotlin/Native: Swift Package Import and Swift Export Alpha

Kotlin/Native gains two Apple platform advances:

• Swift Package Import (Experimental): Kotlin/Native code can now directly import and use Swift packages as dependencies, eliminating the Objective-C bridging requirement for many Swift frameworks.
• Swift Export Alpha: The direct Swift/Kotlin interop bridge — bypassing ObjC headers — moves to Alpha with improved concurrency support, including @MainActor and async/await compatibility improvements.

Gradle and Build Tooling

• Gradle 9.5.0 compatibility: Full support for the latest Gradle release.
• Build Tools API: Kotlin Build Tools API receives stability updates for toolchain integrators.
• Consistent .klib inline function behavior: More predictable inlining semantics during .klib compilation, reducing surprises in multiplatform module publishing.
• No more deprecation warnings on import last segments: Kotlin 2.4.0 stops emitting deprecation warnings when importing a deprecated symbol at the last segment of an import path — a long-standing quality-of-life fix.

Why This Release Matters for Enterprise Teams

FAQ

About the Author

Conclusion

Kotlin 2.4.0 is a landmark stabilization release. Context parameters and explicit backing fields are ready for production. Java 26 support keeps enterprise JVM stacks current. And Wasm's Component Model integration points toward Kotlin's future as a polyglot systems language extending beyond Android and the JVM.

To track Kotlin's evolution and its role in AI-native backend engineering, see my analysis of active RAG and multi-hop query planning and AI agents production memory patterns.

Vatsal Shah

Technical Project Manager & Solution Architect

I write code, ship agentic systems, and advise boards from India and global HQ — 15+ years across BFSI, GCC, and Fortune-scale cloud programs. If you need architecture that survives audit, start here.

View credentials →