m06-error-handling

Use std::optional for C++ error handling when a function might return no value without a specific failure cause, and use std::expected when you need to return a value or propagate a detailed error code. This distinction makes failures explicit and debuggable.

Use noexcept and RAII to ensure resource safety during C++ exceptions by marking non-throwing functions noexcept and letting object destructors automatically release resources. This prevents resource leaks and silent failures when unwinding the call stack.

The best way to handle errors across C++ library boundaries is to standardize error handling patterns explicitly, choosing between exceptions, error codes, or std::expected based on whether the error is recoverable or fatal, ensuring safe integration and improved debuggability.

Distinguish recoverable errors from fatal C++ failures by using try/catch, std::optional, or std::expected for recoverable conditions, and applying assert or noexcept for fatal program states that should immediately halt execution instead of propagating silently.

Refactor C++ code returning std::optional to std::expected by changing the return type to std::expected<T, E> and replacing empty optional returns with explicit error types. This provides clear failure context and applies noexcept where appropriate to guarantee non-throwing behavior.