Open abrenneke opened 1 year ago
how would unwrapOrElse
work? what would be the type of val
in an error scenario?
is the idea that unwrapOrElse
would always throw in the error case? if not, how do you handle the fact that val
continues to live on in outer scope in an error situation?
i like the idea of these ergonomics but i don't see anyway to not return control to the outer scope unless you are always throwing after otherFn()
is called.
I'm liking the lib so far! What are your thoughts on
orElse
methods? Right now if I want to have errors fallback I do:But that could be made a little more ergonomic if it was something like:
Or the equivalent unwrap:
I get that it's a balance of keeping the lib small and having things be ergonomic - rust has soo many Result methods 😆