/// Wrap the error value with additional context.

    /// Create a new error from an error message to wrap the existing error.

    /// For attaching context to a `Result` as it is propagated, the
    /// [`WrapErr`][crate::WrapErr] extension trait may be more convenient than
    /// this function.

    /// For attaching a higher level error message to a `Result` as it is propagated, the
    /// [`WrapErr`][crate::WrapErr] extension trait may be more convenient than this function.

    /// The primary reason to use `error.context(...)` instead of
    /// `result.context(...)` via the `WrapErr` trait would be if the context
    /// needs to depend on some data held by the underlying error:

    /// The primary reason to use `error.wrap_err(...)` instead of `result.wrap_err(...)` via the
    /// `WrapErr` trait would be if the message needs to depend on some data held by the underlying
    /// error:

    ///         let context = format!(

    ///         let message = format!(

    ///         eyre::ErrReport::new(error).wrap_err(context)

    ///         eyre::ErrReport::new(error).wrap_err(message)

    /// For errors with context, this method returns true if `E` matches the
    /// type of the context `D` **or** the type of the error on which the
    /// context has been attached. For details about the interaction between
    /// context and downcasting, [see here].

    /// For errors constructed from messages, this method returns true if `E` matches the type of
    /// the message `D` **or** the type of the error on which the message has been attached. For
    /// details about the interaction between message and downcasting, [see here].

//! - Attach context to help the person troubleshooting the error understand
//!   where things went wrong. A low-level error like "No such file or
//!   directory" can be annoying to debug without more context about what higher
//!   level step the application was in the middle of.

//! - Create new errors from messages to help the person troubleshooting the error understand where
//! things went wrong. A low-level error like "No such file or directory" can be annoying to
//! directly and often benefit from being wrapped with higher level error messages.

/// When you print an error object using "{}" or to_string(), only the outermost
/// underlying error or context is printed, not any of the lower level causes.
/// This is exactly as if you had called the Display impl of the error from
/// which you constructed your eyre::ErrReport.

/// When you print an error object using "{}" or to_string(), only the outermost underlying error
/// is printed, not any of the lower level causes. This is exactly as if you had called the Display
/// impl of the error from which you constructed your eyre::ErrReport.

///             // correctly succeed even with the context in between.

///             // correctly succeed even with the message in between.

///             // HelperFailed is the context that has been attached to

///             // HelperFailed is the message that has been attached to