Platform types and null safety in Kotlin - Cheat Sheet & Quick Revision

Recall & Review

beginner

What are platform types in Kotlin?

Platform types are types coming from Java code where Kotlin cannot be sure if the value can be null or not. Kotlin treats them as types that can be either nullable or non-nullable, so you have to be careful when using them.

beginner

How does Kotlin handle null safety with platform types?

Kotlin does not enforce null safety on platform types because it cannot be sure if the value is nullable or not. You must manually check for null or use safe calls to avoid errors.

intermediate

What happens if you assign a platform type to a non-nullable Kotlin variable without checking for null?

If the platform type value is actually null, your program will throw a NullPointerException at runtime because Kotlin assumes it is not null.

beginner

How can you safely use a platform type value in Kotlin?

You can use safe calls (?.), the Elvis operator (?:), or explicit null checks to handle possible null values from platform types safely.

intermediate

Why does Kotlin have platform types instead of just treating all Java types as nullable?

Because many Java APIs do not specify nullability, Kotlin uses platform types to allow flexibility. Treating all Java types as nullable would require unnecessary null checks and reduce code clarity.

What is a platform type in Kotlin?

A A type from Java code with unknown nullability

B A Kotlin type that is always non-null

C A Kotlin type that is always nullable

D A special Kotlin type for collections

Platform types come from Java code where Kotlin cannot be sure if the value can be null or not.

If you assign a platform type to a non-nullable Kotlin variable without checking, what can happen?

A Compile-time error

B The program crashes immediately on start

C The value becomes non-null automatically

D NullPointerException at runtime

If the platform type value is null, Kotlin will throw a NullPointerException at runtime.

Which Kotlin operator helps safely access a platform type that might be null?

A ?.

B ?:

C !!

D ==

The safe call operator (?.) allows you to safely access properties or methods on nullable or platform types.

Why doesn't Kotlin treat all Java types as nullable by default?

A Because Kotlin ignores Java nullability

B Because Java types are always non-null

C To avoid unnecessary null checks and keep code clear

D Because Kotlin does not support null safety

Treating all Java types as nullable would force many unnecessary null checks and reduce code clarity.

What should you do when using platform types to avoid null pointer exceptions?

A Convert platform types to strings

B Use safe calls or null checks

C Always use !! operator

D Ignore null safety

Using safe calls or explicit null checks helps avoid null pointer exceptions with platform types.

Explain what platform types are in Kotlin and why they exist.

Think about how Kotlin works with Java code that does not specify nullability.

Describe how to safely handle platform types in Kotlin to avoid runtime errors.

Consider Kotlin operators that help with nullable values.

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