Why Custom error types in Rust? - Purpose & Use Cases

The Big Idea

What if your program could tell you exactly why it failed, like a helpful friend?

The Scenario

Imagine you write a program that talks to a database, reads files, and talks to the internet. When something goes wrong, you just get a generic error message like "Something went wrong." It's like getting a "bad news" letter without knowing what exactly happened.

The Problem

Using only generic errors is slow and frustrating. You have to guess what caused the problem. It's like trying to fix a broken car without knowing if the engine, tires, or brakes failed. This wastes time and can cause more mistakes.

The Solution

Custom error types let you create clear, specific error messages for each problem. It's like having a detailed report that says "Engine failure" or "Flat tire." This helps you quickly find and fix the exact issue.

Before vs After

✗ Before

fn do_something() -> Result<(), String> {
    Err("Error".to_string())
}

✓ After

enum MyError {
    IoError(std::io::Error),
    ParseError(String),
}

fn do_something() -> Result<(), MyError> {
    Err(MyError::ParseError("Invalid input".to_string()))
}

What It Enables

Custom error types let your program explain exactly what went wrong, making debugging and fixing problems much faster and easier.

Real Life Example

Think of a banking app that tells you if a transaction failed because of insufficient funds, network issues, or invalid account details. Each error type helps the app respond correctly and guide the user.

Key Takeaways

Generic errors hide the real problem and slow down fixing.

Custom error types give clear, specific error information.

This clarity helps programmers find and fix bugs faster.

Practice

1. What is the main purpose of creating a custom error type in Rust?

easy

A. To automatically fix bugs in the code.

B. To make the program run faster by avoiding errors.

C. To replace the need for using Result types.

D. To describe specific problems in your program with clear error messages.

Solution

1. Step 1: Understand the role of custom errors

   Custom error types help programmers describe specific problems clearly in their code.

2. Step 2: Compare with other options

   Custom errors do not speed up code, fix bugs automatically, or replace Result types; they provide clear error descriptions.

3. Final Answer:

   To describe specific problems in your program with clear error messages. -> Option D

4. Quick Check:

   Custom error purpose = clear problem description [OK]

Hint: Custom errors explain problems clearly, not fix or speed up code [OK]

Common Mistakes:

• Thinking custom errors fix bugs automatically
• Confusing custom errors with performance improvements
• Believing custom errors replace Result types

2. Which of the following is the correct way to start defining a custom error enum in Rust?

easy

A. enum MyError { Io(std::io::Error), Parse(std::num::ParseIntError) }

B. struct MyError { message: String }

C. fn MyError() -> Error {}

D. class MyError { error: String }

Solution

1. Step 1: Identify Rust enum syntax

   Rust uses enum to define custom error types with variants, like Io(std::io::Error).

2. Step 2: Check other options

   struct is for data structures, fn is for functions, and class is not Rust syntax.

3. Final Answer:

   enum MyError { Io(std::io::Error), Parse(std::num::ParseIntError) } -> Option A

4. Quick Check:

   Custom error enum = enum with variants [OK]

Hint: Custom errors use enum with variants, not struct or class [OK]

Common Mistakes:

• Using struct instead of enum for error variants
• Trying to define errors as functions
• Using class keyword which is invalid in Rust

3. What will be the output of this Rust code snippet?

use std::fmt;

#[derive(Debug)]
enum MyError {
    NotFound,
    PermissionDenied,
}

impl fmt::Display for MyError {
    fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result {
        match self {
            MyError::NotFound => write!(f, "Item not found"),
            MyError::PermissionDenied => write!(f, "Permission denied"),
        }
    }
}

fn main() {
    let err = MyError::NotFound;
    println!("Error: {}", err);
}

medium

A. Error: NotFound

B. Error: Item not found

C. Error: Permission denied

D. Compilation error due to missing trait

Solution

1. Step 1: Understand Display implementation

   The fmt method matches MyError::NotFound and writes "Item not found" to the formatter.

2. Step 2: Check main output

   Printing err with {} uses Display, so output is "Error: Item not found".

3. Final Answer:

   Error: Item not found -> Option B

4. Quick Check:

   Display prints custom message = "Item not found" [OK]

Hint: Display trait controls {} output, matching variant message shown [OK]

Common Mistakes:

• Expecting Debug output instead of Display
• Confusing variant name with message
• Assuming compilation error without Display trait

4. Identify the error in this custom error implementation:

enum MyError {
    Io(std::io::Error),
}

impl std::fmt::Display for MyError {
    fn fmt(&self, f: &mut std::fmt::Formatter) -> std::fmt::Result {
        write!(f, "{}", self.0)
    }
}

medium

A. Cannot access self.0 because enum variant is not destructured.

B. Missing implementation of Debug trait.

C. Display trait cannot be implemented for enums.

D. write! macro requires a string literal, not a variable.

Solution

1. Step 1: Check how self.0 is accessed

   In an enum, you cannot directly access self.0 without matching or destructuring the variant.

2. Step 2: Understand correct pattern

   You must match self to get the inner std::io::Error value before using it in write!.

3. Final Answer:

   Cannot access self.0 because enum variant is not destructured. -> Option A

4. Quick Check:

   Enum variant fields need matching before access [OK]

Hint: Match enum variants before accessing inner fields [OK]

Common Mistakes:

• Trying to access enum fields directly without match
• Thinking Display can't be implemented for enums
• Assuming Debug trait is mandatory for Display

5. You want to create a custom error type that can hold either an IO error or a parsing error, and provide user-friendly messages. Which of these is the best complete approach?

hard

A. Create separate error structs for IO and parse errors without enums, and use panic! for messages.

B. Use a struct with two optional fields for IO and parse errors, and implement Display only.

C. Define an enum with variants for each error type, implement Display with match arms for messages, and implement std::error::Error.

D. Use a type alias for Result with String errors and skip custom error types.

Solution

1. Step 1: Choose enum for multiple error types

   An enum cleanly groups different error variants like IO and parse errors.

2. Step 2: Implement Display and std::error::Error traits

   Display provides friendly messages; implementing std::error::Error integrates with Rust error handling.

3. Final Answer:

   Define an enum with variants for each error type, implement Display with match arms for messages, and implement std::error::Error. -> Option C

4. Quick Check:

   Enum + Display + Error trait = best custom error pattern [OK]

Hint: Use enum + Display + Error trait for best custom error design [OK]

Common Mistakes:

• Using struct with optional fields causing confusion
• Skipping std::error::Error trait implementation
• Using panic! instead of proper error handling