Rust provides two methods for handling unrecoverable errors unwrap and expect, they can be used on both Result and Option types, they will trigger a panic! if the value is an Err(E) variant for Result<T, E> or a None variant for Option<T>
These methods extract the inner value but terminate the program if the operation fails. They are particularly useful for quick prototyping or situations where an error is truly unrecoverable.
In this challenge, you will interact with file operations to demonstrate the use of unwrap and expect. Instead of directly working with Result or Option, you will use standard library functions that return these types and handle their results using unwrap and expect.
Implement the following functions:
read_file_to_string: This function takes a file path as input, attempts to read its contents, and returns the contents as a String. Use expect to handle any file I/O errors with a custom error message of exactly Failed to read file: <path>.get_env_variable: This function retrieves the value of an environment variable by name. Use unwrap to panic if the variable is not set.expect provides a way to add context to your panics, which can help with debugging.unwrap is more concise but less descriptive when errors occur.If you're stuck, here are some hints to help you solve the challenge:
std::fs::read_to_string(path) to read the contents of a file. It returns a Result<String, std::io::Error>.std::env::var(key) to retrieve an environment variable. It returns a Result<String, std::env::VarError>..expect() to add a custom error message when handling a Result..unwrap() for a quick, less descriptive error handling method.