@JvmStatic

## The problem: Kotlin has no `static` Kotlin removed the `static` keyword. Where Java uses static members, Kotlin uses a **companion object** (one per class, declared with `companion object { ... }`) or a **named object** (`object Foo { ... }`, a singleton). Both are real objects — instances — not static containers. ## What the compiler emits by default Given: ```kotlin class Foo { companion object { fun bar() = 42 } } ``` The compiler creates a nested class `Foo$Companion` and a single static field `Foo.Companion` holding that singleton. `bar()` becomes an **instance** method on `Foo$Companion`. From Kotlin you write `Foo.bar()` and the compiler routes it through the singleton automatically. From **Java**, though, there is no such sugar, so you must write the verbose, surprising: ```java Foo.Companion.bar(); ``` ## What `@JvmStatic` changes Annotating the member with `@JvmStatic`: ```kotlin class Foo { companion object { @JvmStatic fun bar() = 42 } } ``` tells the compiler to **also** emit a real `static` method `bar()` directly on the **outer class** `Foo`. Now Java can call: ```java Foo.bar(); // clean — calls the generated static method ``` The `Foo.Companion.bar()` form still exists too; `@JvmStatic` is purely additive at the bytecode level. ## Key facts - It affects **only generated JVM bytecode for Java callers**. Kotlin call sites already used `Foo.bar()` and are unchanged. - It works on members of a **companion object** or a **named `object`**. - It applies to **functions and properties** (for a property it generates a static getter/setter). - It is one of several JVM interop annotations alongside `@JvmField`, `@JvmName`, `@JvmOverloads`, and `@Throws`.