Result type for functional error handling in Kotlin

Introduction

The Result type helps you handle success or failure in a clear way without crashing your program.

When you want to run a function that might fail and handle errors safely.

When you want to avoid using try-catch blocks everywhere in your code.

When you want to pass success or error results between functions clearly.

When you want to write cleaner code that shows success or failure explicitly.

Syntax

Kotlin

fun someFunction(): Result<Type> {
    return try {
        val value = /* do something that might fail */
        Result.success(value)
    } catch (e: Exception) {
        Result.failure(e)
    }
}

Use Result.success(value) to return a successful result.

Use Result.failure(exception) to return an error result.

Examples

This function returns success if division is possible, or failure if dividing by zero.

Kotlin

fun divide(a: Int, b: Int): Result<Int> {
    return if (b == 0) {
        Result.failure(IllegalArgumentException("Cannot divide by zero"))
    } else {
        Result.success(a / b)
    }
}

Use onSuccess and onFailure to handle the result.

Kotlin

val result = divide(10, 2)
result.onSuccess { value -> println("Result is $value") }
      .onFailure { error -> println("Error: ${error.message}") }

Sample Program

This program tries to divide numbers and prints success or failure messages using the Result type.

Kotlin

fun divide(a: Int, b: Int): Result<Int> {
    return if (b == 0) {
        Result.failure(IllegalArgumentException("Cannot divide by zero"))
    } else {
        Result.success(a / b)
    }
}

fun main() {
    val result1 = divide(10, 2)
    val result2 = divide(10, 0)

    result1.onSuccess { println("Success: $it") }
           .onFailure { println("Failure: ${it.message}") }

    result2.onSuccess { println("Success: $it") }
           .onFailure { println("Failure: ${it.message}") }
}

Important Notes

The Result type helps avoid crashes by handling errors explicitly.

You can chain onSuccess and onFailure to react to results.

Use getOrElse or getOrNull to extract values safely.

Summary

Result type wraps success or failure in one object.

Use Result.success and Result.failure to create results.

Handle results with onSuccess and onFailure for clear code.

Practice

1. What does the Kotlin Result type represent in functional error handling?

easy

A. A special type of exception thrown during errors

B. An object that holds either a success value or a failure exception

C. A function that always returns a Boolean

D. A list of all errors encountered during execution

Solution

1. Step 1: Understand the purpose of Result type

   The Result type is designed to wrap either a successful outcome or an error, making error handling explicit and functional.

2. Step 2: Identify what Result holds

   Result holds either a success value or a failure exception, not a list or a Boolean or an exception thrown directly.

3. Final Answer:

   An object that holds either a success value or a failure exception -> Option B

4. Quick Check:

   Result = success or failure [OK]

Hint: Result always wraps success or failure, not exceptions thrown [OK]

Common Mistakes:

• Thinking Result is an exception type
• Confusing Result with Boolean return
• Assuming Result holds multiple errors

2. Which of the following is the correct way to create a successful Result object in Kotlin?

easy

A. Result.makeSuccess(value)

B. Result.ofSuccess(value)

C. Result.createSuccess(value)

D. Result.success(value)

Solution

1. Step 1: Recall the Kotlin Result API

   Kotlin provides Result.success(value) to create a successful Result wrapping the value.

2. Step 2: Check method names

   Only Result.success is the correct and existing method; others are invalid.

3. Final Answer:

   Result.success(value) -> Option D

4. Quick Check:

   Use Result.success() to wrap success [OK]

Hint: Use Result.success() to wrap success values [OK]

Common Mistakes:

• Using non-existent methods like Result.ofSuccess
• Confusing with factory methods
• Trying to create Result with constructors

3. What will be the output of this Kotlin code?

val result = runCatching { 10 / 0 }
result.onSuccess { println("Success: $it") }
result.onFailure { println("Failure: ${it.message}") }

medium

A. Failure: / by zero

B. Success: 0

C. No output

D. RuntimeException thrown

Solution

1. Step 1: Understand runCatching behavior

   runCatching executes the block and catches exceptions, wrapping them in Result.failure.

2. Step 2: Analyze division by zero

   10 / 0 throws an ArithmeticException with message "/ by zero" which is caught and triggers onFailure.

3. Final Answer:

   Failure: / by zero -> Option A

4. Quick Check:

   Exception caught triggers onFailure [OK]

Hint: runCatching catches exceptions and calls onFailure [OK]

Common Mistakes:

• Expecting program to crash with exception
• Thinking onSuccess runs despite error
• Ignoring exception message in output

4. Identify the error in this Kotlin code using Result for error handling:

fun divide(a: Int, b: Int): Result<Int> {
    return try {
        Result.success(a / b)
    } catch (e: Exception) {
        Result.failure(e)
    }
}

val result = divide(10, 0)
result.onSuccess { println("Result: $it") }
      .onFailure { println("Error: ${it.message}") }

medium

A. Cannot chain onSuccess and onFailure directly on Result

B. Should catch ArithmeticException instead of Exception

C. Result.failure should not be used inside catch block

D. No error, code works correctly

Solution

1. Step 1: Check chaining onSuccess and onFailure

   In Kotlin, onSuccess and onFailure are extension functions returning Unit, so chaining them directly causes a compile error.

2. Step 2: Verify other parts

   Try-catch with Result.success and Result.failure is correct; catching Exception is acceptable; Result.failure is valid.

3. Final Answer:

   Cannot chain onSuccess and onFailure directly on Result -> Option A

4. Quick Check:

   onSuccess and onFailure return Unit, no chaining [OK]

Hint: onSuccess/onFailure return Unit, cannot chain calls [OK]

Common Mistakes:

• Trying to chain onSuccess and onFailure
• Thinking catch block must catch ArithmeticException only
• Misusing Result.failure inside catch

5. You want to write a Kotlin function that returns a Result wrapping the parsed integer from a string, or a failure if parsing fails. Which implementation correctly uses Result for this purpose?

hard

A. fun parseInt(str: String): Result<Int> = Result.failure(NumberFormatException())

B. fun parseInt(str: String): Result<Int> = Result.success(str.toIntOrNull() ?: throw NumberFormatException())

C. fun parseInt(str: String): Result<Int> = try { Result.success(str.toInt()) } catch (e: NumberFormatException) { Result.failure(e) }

D. fun parseInt(str: String): Int = str.toIntOrNull() ?: -1

Solution

1. Step 1: Understand the goal

   The function should return Result wrapping success if parsing works, or failure if it throws NumberFormatException.

2. Step 2: Analyze each option

   fun parseInt(str: String): Result<Int> = try { Result.success(str.toInt()) } catch (e: NumberFormatException) { Result.failure(e) } uses try-catch to wrap success or failure correctly. fun parseInt(str: String): Result<Int> = Result.success(str.toIntOrNull() ?: throw NumberFormatException()) throws exception outside Result.failure, breaking functional style. fun parseInt(str: String): Result<Int> = Result.failure(NumberFormatException()) always returns failure, ignoring input. fun parseInt(str: String): Int = str.toIntOrNull() ?: -1 returns Int, not Result.

3. Final Answer:

   fun parseInt(str: String): Result<Int> = try { Result.success(str.toInt()) } catch (e: NumberFormatException) { Result.failure(e) } -> Option C

4. Quick Check:

   Try-catch with Result.success/failure wraps parsing safely [OK]

Hint: Use try-catch with Result.success and Result.failure for safe parsing [OK]

Common Mistakes:

• Throwing exceptions instead of wrapping in Result.failure
• Returning plain Int instead of Result<Int>
• Always returning failure ignoring input