I have the exact same use case as @zackw . My use case is a gui application, I handle the error by logging as soon as I know for sure know how to handle it and then maybe present the user with a popup message. I don't want to lose the fact that this is a Result and higher up in the call stack (which is usually just one level - page rendering) should not attempt to log or understand the error, just know that an error occurred. So yes there really is nothing to say about the failure, which is the motivation for using.