Platform types and null safety in Kotlin

Introduction

Platform types help Kotlin work safely with Java code that may or may not allow null values. They let Kotlin know when it should be careful about nulls.

When calling Java code from Kotlin and you don't know if a value can be null.

When you want to avoid crashes caused by unexpected null values from Java libraries.

When mixing Kotlin and Java code in the same project and need safe null handling.

When you want Kotlin to help you catch possible null errors at compile time.

When you want to gradually add null safety to existing Java code.

Syntax

Kotlin

val someValue: String = javaMethod()
val someNullableValue: String? = javaMethod()

Platform types appear when Kotlin calls Java methods without explicit nullability annotations.

You can treat platform types as nullable or non-nullable, but Kotlin warns you to be careful.

Examples

Here, Kotlin assumes the Java method returns a non-null String, so you can use it safely.

Kotlin

val name: String = javaGetName()  // Platform type treated as non-null
println(name.length)

Here, Kotlin treats the Java return as nullable and checks for null before using it.

Kotlin

val name: String? = javaGetName()  // Platform type treated as nullable
if (name != null) {
    println(name.length)
}

If you ignore null safety, you might get a crash if the Java method returns null.

Kotlin

val name = javaGetName()  // Platform type, no explicit nullability
println(name.length)  // Risk of NullPointerException if null

Sample Program

This program simulates calling a Java method that returns null. Kotlin treats it as non-null, so accessing length causes a crash.

Kotlin

fun javaGetName(): String? = null  // Simulate Java method that may return null

fun main() {
    val name = javaGetName()  // Platform type, no explicit nullability
    println("Name length: ${name!!.length}")
}

Important Notes

Platform types let Kotlin be flexible but require you to be careful with nulls from Java.

Use explicit null checks or annotations in Java to improve safety.

When unsure, treat platform types as nullable to avoid crashes.

Summary

Platform types appear when Kotlin calls Java code without clear null info.

They can be treated as nullable or non-nullable, but this can cause risks.

Always check for null or add annotations to keep your Kotlin code safe.

Practice

1. What is a platform type in Kotlin when interacting with Java code?

easy

A. A type with unknown nullability coming from Java code

B. A Kotlin type that is always non-nullable

C. A Kotlin type that is always nullable

D. A special Kotlin type used only in multiplatform projects

Solution

1. Step 1: Understand Kotlin-Java interoperability

   Kotlin calls Java code but Java does not specify nullability clearly.

2. Step 2: Define platform type meaning

   Platform types represent types from Java with unknown nullability, so Kotlin treats them flexibly but unsafely.

3. Final Answer:

   A type with unknown nullability coming from Java code -> Option A

4. Quick Check:

   Platform type = unknown nullability [OK]

Hint: Platform types come from Java with unclear null info [OK]

Common Mistakes:

• Thinking platform types are always nullable
• Assuming platform types are always non-nullable
• Confusing platform types with Kotlin multiplatform types

2. Which Kotlin syntax correctly declares a variable that can hold a platform type from Java and safely handle nulls?

easy

A. val name: String = javaMethod()

B. val name: String!! = javaMethod()

C. val name: String? = javaMethod()

D. val name: String? = null!!

Solution

1. Step 1: Recognize platform type usage

   Java method returns a platform type, which can be nullable or not.

2. Step 2: Choose safe Kotlin declaration

   Declaring as nullable String? allows safe null handling from platform types.

3. Final Answer:

   val name: String? = javaMethod() -> Option C

4. Quick Check:

   Nullable type for platform type = safe [OK]

Hint: Use nullable type to safely hold platform types [OK]

Common Mistakes:

• Using non-nullable type without null checks
• Using !! which causes exceptions if null
• Using invalid syntax like null!!

3. Given this Kotlin code calling a Java method returning a platform type:

fun printLength() {
    val text: String = javaMethod()
    println(text.length)
}

What happens if javaMethod() returns null?

medium

A. The program compiles but does nothing

B. The program prints 0

C. The program prints "null"

D. The program throws a NullPointerException at runtime

Solution

1. Step 1: Analyze variable declaration

   Variable text is declared as non-nullable String but assigned platform type from Java.

2. Step 2: Consider null return from Java

   If javaMethod() returns null, Kotlin does not check at compile time, but accessing text.length causes NullPointerException.

3. Final Answer:

   The program throws a NullPointerException at runtime -> Option D

4. Quick Check:

   Non-null platform type + null value = runtime exception [OK]

Hint: Non-null platform types can cause runtime null errors [OK]

Common Mistakes:

• Assuming Kotlin prevents null assignment from platform types
• Thinking it prints 0 or "null" instead of crashing
• Ignoring runtime exceptions from platform types

4. Identify the error in this Kotlin code using a platform type:

val length: Int = javaMethod()?.length

where javaMethod() returns a platform type String!.

medium

A. The expression can return null but assigned to non-nullable Int

B. No error, code is correct

C. Platform types cannot be assigned to Int variables

D. Safe call operator ?. cannot be used on platform types

Solution

1. Step 1: Understand the expression type

   javaMethod() returns platform type String!, so javaMethod()?.length returns Int? (nullable Int).

2. Step 2: Check assignment compatibility

   Assigning nullable Int? to non-nullable Int variable length causes a type mismatch error.

3. Final Answer:

   The expression can return null but assigned to non-nullable Int -> Option A

4. Quick Check:

   Nullable result assigned to non-null variable = error [OK]

Hint: Nullable result must not assign to non-null variable [OK]

Common Mistakes:

• Thinking safe call ?. is invalid on platform types
• Ignoring nullability mismatch in assignment
• Assuming platform types cannot be used with Int

5. You have a Java method String getName() that may return null. How should you declare and use it in Kotlin to avoid null pointer exceptions and keep null safety?

hard

A. Declare as val name: String = javaMethod() and use name.length

B. Declare as val name: String? and check if (name != null) before use

C. Declare as val name: String!! and use name.length directly

D. Declare as val name: String and use name?.length ?: 0

Solution

1. Step 1: Recognize Java method nullability

   Java method may return null, so Kotlin platform type is uncertain.

2. Step 2: Choose safe Kotlin declaration and usage

   Declare as nullable String? and check for null before accessing properties to avoid exceptions.

3. Final Answer:

   Declare as val name: String? and check if (name != null) before use -> Option B

4. Quick Check:

   Nullable declaration + null check = safe usage [OK]

Hint: Use nullable type and explicit null check for Java returns [OK]

Common Mistakes:

• Using non-nullable type without null checks
• Using !! which risks runtime exceptions
• Misusing safe call with non-nullable declaration