Kotlin Double Exclamation Operator (!!)

Kotlin is well-known for its powerful null safety features that help developers avoid the dreaded NullPointerException (NPE). One of the most talked-about—and often misused—features is the Kotlin Double Exclamation Operator (!!).

This operator explicitly tells the compiler that you are certain the value is not null at that point in the code. If the value happens to be null during execution, it will throw a NullPointerException (NPE), which is a runtime crash

What Is Kotlin Double Exclamation Operator (!!)?

The Double Exclamation Operator (!!) in Kotlin is used to explicitly tell the compiler that a nullable variable is not null at a specific point in the code.

If the value turns out to be null at runtime, Kotlin will throw a NullPointerException.

Simple Definition

• !! converts a nullable type (T?) into a non-nullable type (T)
• If the value is null, the app crashes with NPE

Why Does Kotlin Have the !! Operator?

Kotlin enforces null safety at compile time, but there are situations where:

• You are absolutely sure a value is not null
• You receive data from legacy Java code
• You want the program to fail fast if an assumption is violated

In such cases, Kotlin provides the !! operator as an escape hatch.

Basic Syntax of Kotlin Double Exclamation

📄

val name: String? = "Kotlin"
val length: Int = name!!
println(length.length)

What Happens Here?

• 📄
  name is nullable (String?)
• 📄
  name!! tells Kotlin it is not null
• The code runs safely if the value exists

But If the Value Is Null…

📄

val name: String? = null
val length = name!!

This will throw a NullPointerException at runtime.

Kotlin !! Operator and NullPointerException

The biggest risk of using the Kotlin double exclamation operator is runtime crashes.

Because of this risk, overusing !! is considered a bad practice.

Real-World Use Cases of Kotlin Double Exclamation

1. Working with Android Views

📄

var button: Button? = findViewById(R.id.myButton)
button!!.setOnClickListener {
    println("Button clicked")
}

Here, the developer assumes the view always exists. If the layout changes, this can crash.

2. Interoperability with Java Code

Java does not enforce null safety. When calling Java methods, Kotlin often returns nullable types.

📄

val userName: String? = javaService.getUserName()
println(userName!!)

This is one of the few cases where !! might be acceptable.

3. Failing Fast for Critical Logic

📄

val config: Config? = loadConfig()
val apiKey = config!!.apiKey

If the configuration is missing, the app should crash immediately.

Common Mistakes When Using Kotlin !!

• Using !! everywhere instead of proper null handling
• Assuming values will never be null
• Ignoring safer alternatives like safe calls or Elvis operator

Safer Alternatives to Kotlin Double Exclamation

1. Safe Call Operator (?.)

📄

val length = name?.length

Returns null instead of crashing.

2. Elvis Operator (?:)

📄

val length = name?.length ?: 0

Provides a default value when null.

3. Let Function

📄

name?.let {
    println(it.length)
}

Executes code only if the value is not null.

When Should You Use Kotlin !!?

• You are 100% sure the value is not null
• You want the program to fail fast
• You are dealing with legacy or Java-based APIs

When Should You Avoid It?

• User input handling
• Network responses
• Database or API data

The Kotlin Double Exclamation Operator (!!) is a powerful but dangerous tool. While it allows developers to override Kotlin’s null safety, it also reintroduces the risk of NullPointerException.

For clean, safe, and maintainable Kotlin code, always prefer safer alternatives and use !! only when absolutely necessary.

Frequently Asked Questions (FAQs)

1. What does !! mean in Kotlin?

The !! operator converts a nullable variable into a non-nullable one and throws a NullPointerException if the value is null.

2. Is using !! considered bad practice?

Overusing it is considered bad practice. It should be used sparingly and only when you are certain the value is not null.

3. Does !! remove null safety in Kotlin?

Yes, it bypasses Kotlin’s null safety checks and shifts the responsibility to the developer.

4. What is the safest alternative to !!?

Safe calls (?.), Elvis operator (?:), and let blocks are safer alternatives.

5. Can !! be used in production code?

Yes, but only in controlled scenarios where null values indicate a serious logic error.