Why Finally block behavior in Kotlin? - Purpose & Use Cases

The Big Idea

What if your program could always clean up after itself, even when things go wrong?

The Scenario

Imagine you are writing a program that opens a file to read data. You manually write code to close the file after reading, but if an error happens, you might forget to close it properly.

The Problem

Without a special way to guarantee cleanup, your program might leave files open or resources locked if an error occurs. This causes bugs, wasted memory, or crashes, and tracking these issues is hard and frustrating.

The Solution

The finally block runs code no matter what happens in the try or catch blocks. It ensures cleanup like closing files or releasing resources always happens, even if errors occur.

Before vs After

✗ Before

try {
  // read file
  // close file manually
} catch (e: Exception) {
  // handle error
  // forgot to close file here
}

✓ After

try {
  // read file
} catch (e: Exception) {
  // handle error
} finally {
  // always close file here
}

What It Enables

It makes your programs safer and more reliable by guaranteeing important cleanup steps always run.

Real Life Example

When downloading a file from the internet, you want to close the connection no matter if the download succeeds or fails. The finally block ensures the connection closes properly every time.

Key Takeaways

The finally block always runs after try and catch.

It helps clean up resources like files or network connections.

This prevents bugs caused by forgetting to release resources.