I note that you did nothing to refute my point about why error-handling-via-return-values is insufficient and instead resort to emotional manipulation and logical fallacies.
This seems to happen a lot in the Rust community when people point out flaws in the language.
> When I say "it doesn't work" I mean that it doesn't allow you to write good code
But you skipped over how you are defining, "good code"? Without that part, "doesn't allow" cannot be evaluated in the context of Java or C++ or Python or Go or Rust.
Apparently you have difficulty with reading comprehension, because my original comment already defines "good code":
> The result type does not work because you have to choose between immediate callers handling failures (they don't always have the context to do so because they're not aware of the context of callers higher up on the call stack) or between propagating all of your error values all the way up the stack to the error handling point and making your program fantastically brittle and insanely hard to refactor.
It's interactions like this that are the reason why my organization isn't adopting Rust.
Defined good code TO YOU. You've failed to recognize there is no objective and universally recognized metric for good code within our industry. The closest thing we have to it is number of defects per line of code and how severe those defects are through CVEs. That's it.
You've mistaken your personal preferences and aesthetic sense for absolute truth.
This seems to happen a lot in the Rust community when people point out flaws in the language.