Why RunCatching for safe execution in Kotlin? - Purpose & Use Cases

The Big Idea

What if you could catch errors without messy try-catch blocks everywhere?

The Scenario

Imagine you have a piece of code that might fail, like reading a file or parsing a number. You try to run it, but if something goes wrong, your whole program crashes or you have to write many lines to catch errors.

The Problem

Handling errors manually means writing lots of try-catch blocks everywhere. This makes your code long, hard to read, and easy to forget error handling. It's like walking on thin ice, always worried about breaking your program.

The Solution

RunCatching wraps your risky code in a safe container. It catches errors for you and lets you handle success or failure smoothly. This keeps your code clean and your program safe from crashes.

Before vs After

✗ Before

try {
    val result = riskyOperation()
    println("Success: $result")
} catch (e: Exception) {
    println("Failed: ${e.message}")
}

✓ After

val result = runCatching { riskyOperation() }
result.onSuccess { println("Success: $it") }
      .onFailure { println("Failed: ${it.message}") }

What It Enables

You can write safer, cleaner code that handles errors gracefully without cluttering your logic.

Real Life Example

When fetching data from the internet, RunCatching helps you try the request and easily manage failures like no connection or bad responses without crashing your app.

Key Takeaways

Manual error handling is repetitive and error-prone.

RunCatching simplifies catching exceptions in one place.

It makes your code cleaner and safer to run.

Practice

1. What is the main purpose of runCatching in Kotlin?

easy

A. To execute code and catch exceptions safely without crashing the program

B. To run code only if a condition is true

C. To create a new thread for running code

D. To convert a value to a string safely

Solution

1. Step 1: Understand what runCatching does

   runCatching runs a block of code and catches any exceptions that happen inside it.

2. Step 2: Identify the main purpose

   This helps keep the program running smoothly by handling errors safely without crashing.

3. Final Answer:

   To execute code and catch exceptions safely without crashing the program -> Option A

4. Quick Check:

   runCatching = safe execution [OK]

Hint: runCatching catches errors to keep code safe [OK]

Common Mistakes:

• Thinking runCatching runs code conditionally
• Confusing runCatching with threading
• Assuming it converts types automatically

2. Which of the following is the correct syntax to use runCatching in Kotlin?

easy

A. val result = runCatching -> someFunction()

B. val result = runCatching(someFunction())

C. val result = runCatching { someFunction() }

D. val result = runCatching.someFunction()

Solution

1. Step 1: Recall the syntax of runCatching

   runCatching takes a lambda block with curly braces to run code safely.

2. Step 2: Match the correct syntax

   val result = runCatching { someFunction() } uses curly braces and calls someFunction() inside, which is correct.

3. Final Answer:

   val result = runCatching { someFunction() } -> Option C

4. Quick Check:

   runCatching uses braces { } [OK]

Hint: Use curly braces {} to pass code block to runCatching [OK]

Common Mistakes:

• Using parentheses instead of braces
• Trying to call runCatching like a function with arrow
• Accessing runCatching as an object

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

val result = runCatching { 10 / 0 }
println(result.isSuccess)

medium

A. true

B. null

C. Exception thrown

D. false

Solution

1. Step 1: Analyze the code inside runCatching

   The code tries to divide 10 by 0, which causes an exception (ArithmeticException).

2. Step 2: Understand runCatching result

   runCatching catches the exception, so no crash happens. The isSuccess property will be false because the block failed.

3. Final Answer:

   false -> Option D

4. Quick Check:

   Exception caught means isSuccess = false [OK]

Hint: Divide by zero causes failure, so isSuccess is false [OK]

Common Mistakes:

• Expecting true because code runs
• Thinking exception is thrown outside runCatching
• Confusing isSuccess with isFailure

4. Identify the error in this Kotlin code using runCatching:

val result = runCatching {
    val number = "abc".toInt()
}
println(result.getOrNull())

medium

A. No error, prints null because conversion fails

B. Throws NumberFormatException outside runCatching

C. Syntax error in runCatching block

D. getOrNull() returns the string "abc"

Solution

1. Step 1: Understand the code inside runCatching

   Trying to convert "abc" to Int causes NumberFormatException, but runCatching catches it.

2. Step 2: Check what getOrNull() returns

   Since exception happened, getOrNull() returns null safely without crashing.

3. Final Answer:

   No error, prints null because conversion fails -> Option A

4. Quick Check:

   Exception caught means getOrNull() = null [OK]

Hint: runCatching catches exceptions, getOrNull returns null on failure [OK]

Common Mistakes:

• Expecting exception to crash program
• Thinking getOrNull returns original string
• Assuming syntax error in code block

5. You want to safely parse a list of strings to integers using runCatching and collect only the successful results. Which Kotlin code snippet correctly does this?

hard

A. val numbers = list.map { runCatching { it.toInt() }.exceptionOrNull() }

B. val numbers = list.map { runCatching { it.toInt() }.getOrNull() }.filterNotNull()

C. val numbers = list.map { it.toInt() }.filter { it != null }

D. val numbers = list.map { runCatching { it.toInt() }.getOrThrow() }

Solution

1. Step 1: Understand the goal

   We want to convert strings to integers safely, ignoring failures, and collect only successful integers.

2. Step 2: Analyze each option

   val numbers = list.map { runCatching { it.toInt() }.getOrNull() }.filterNotNull() uses runCatching to catch exceptions, then getOrNull() returns integer or null, and filterNotNull() removes nulls, collecting only successful parses.

3. Final Answer:

   val numbers = list.map { runCatching { it.toInt() }.getOrNull() }.filterNotNull() -> Option B

4. Quick Check:

   Safe parse + filter null = val numbers = list.map { runCatching { it.toInt() }.getOrNull() }.filterNotNull() [OK]

Hint: Use getOrNull() then filterNotNull() to keep successful parses [OK]

Common Mistakes:

• Using getOrThrow() which throws on failure
• Filtering nulls before catching exceptions
• Using exceptionOrNull() which returns exceptions, not values