Deep Kotlin tutorial covering Any, Unit, Nothing, type hierarchy with examples, diagram, mistakes, and interview answers.

Any, Unit, and Nothing

What is Any, Unit, and Nothing?

Any, Unit, and Nothing is an important Kotlin topic from 1.2 Immutability, Null Safety, and Type System. In this lesson we focus only on the concepts that belong together: Any, Unit, Nothing, type hierarchy, no normal return. This keeps the lesson deep enough for interviews but not mixed with unrelated ideas.

Why students should learn it

• Understand Any, Unit, and Nothing in simple language
• Use Any in real Kotlin or Android code
• Explain Any, Unit, and Nothing in interviews with examples and trade-offs

How it works

Any, Unit, and Nothing: Any, Unit, Nothing, type hierarchy, no normal return works through Kotlin's type system. The compiler uses type information to warn you before runtime. When the type says a value may be missing, changing, or unknown because it came from Java, your code must handle that explicitly.

1. Identify what problem Any, Unit, and Nothing: Any, Unit, Nothing, type hierarchy, no normal return solves.
2. Write the smallest Kotlin snippet that demonstrates it.
3. Add one Android or JVM use case where it matters.
4. Compare it with a similar concept so the difference is clear.
5. Finish by naming one common mistake and the safer alternative.

Interview tip: keep the answer simple first, then add example, trade-off, and mistake.

Types / Classification

• Any: core concept in this lesson
• Unit: core concept in this lesson
• Nothing: core concept in this lesson
• type hierarchy: core concept in this lesson
• no normal return: core concept in this lesson
• Non-null type: value should exist
• Nullable type: value can be missing
• Safe access: handles absence

Important differences

Diagram

flowchart TD
A["1.2 Immutability, Null Safety, and Type System"] --> B["Any, Unit, and Nothing"]
B --> C["Why it exists"]
C --> D["How it works in Kotlin"]
D --> E["Android or JVM example"]
E --> F["Mistakes and interview answer"]

Examples

Safe nullable handling

fun displayName(name: String?): String {
return name?.trim()?.takeIf { it.isNotEmpty() } ?: "Guest"
}

val is not deep immutability

val names = mutableListOf("Asha")
names.add("Riya") // object still changes

When to use it

Use it when: Reach for this when it makes your code clearer, safer, or easier for the next developer to follow.

Avoid it when: Skip it when a simpler, more familiar approach already solves the problem without extra ceremony.

Common mistakes

• Using !! to silence compiler warnings
• Thinking val makes a mutable object immutable
• Trusting Java platform types without checks
• Returning null when a sealed result would explain failure
• Smart-casting mutable properties that can change

Interview questions

Read each answer in four parts: simple answer, code example, trade-off, and common mistake.

fun displayName(name: String?): String {
return name?.trim()?.takeIf { it.isNotEmpty() } ?: "Guest"
}

val names = mutableListOf("Asha")
names.add("Riya") // object still changes

fun displayName(name: String?): String {
return name?.trim()?.takeIf { it.isNotEmpty() } ?: "Guest"
}

fun displayName(name: String?): String {
return name?.trim()?.takeIf { it.isNotEmpty() } ?: "Guest"
}

val names = mutableListOf("Asha")
names.add("Riya") // object still changes

Practice task

Write one Kotlin example for Any, Unit, and Nothing. Then explain it using: what is it, how it works, where it is used, mistake to avoid, and one interview answer.