any appetite for `.unwrap()` that prints the err value?

Occasionally I have critical errors that cannot be remediated so i’d like to .unwrap(), but I have already captured valuable information in the Result’s Error type that get ignored in the UnwrapError.

Rather than checking for an error, then raising a new error with the captured message I created a .unwrap_print() function (not a great name) to relay this information:

from result import Result, Ok, Err, UnwrapError
from typing import NoReturn

 def unwrap_print(self) -> NoReturn:
    """
    Raises an `UnwrapError` but prints the error value.
    """
    raise UnwrapError(
        self,
        f"Called `Result.unwrap()` on an `Err` value:: {self.value.__repr__()}",
    )

Err.unwrap_print = unwrap_print  # type: ignore

>>> f.unwrap_print()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<stdin>", line 1, in unwrap_print
result.result.UnwrapError: Called `Result.unwrap()` on an `Err` value:: ValueError('testing')

Is this something that we can either add to the existing .unwrap() method or possibly add as a new method? I’m willing to make the PR but just wanted to see if there were any design constraints you’ve already considered first.

[noxasaxon]

it looks like the same behavior happens with .expect("msg") as well

[noxasaxon]

yeah i can make a PR later today!