iex

> you can still ignore the return value Only when you don't need the Ok value from the Result (in other words, only when you have Result<(), E>). You can't get any other Ok(T) out of thin air in the Err case. You must handle (exclude) the Err case in order to unwrap the T and proceed with it. > It also litters your code with branches, so not ideal for either I-cache or performance. That's simply an implementation/ABI issue. See https://github.com/iex-rs/iex/ Language semantics-wise, Result and `?` are superior to automatically propagated exceptions.

iex [0] might be potentially relevant here. From what I understand it basically implements this bit: > Finally, another option is to say that -> Result<T, E> behaves exactly as -> T ABI-wise, no error affordances whatsoever. Instead, when returning an error, rather than jumping to the return address, we look it up in the side table to find a corresponding error recovery address, and jump to that. Stack unwinding! And at least based on the listed benchmarks it can indeed result in better performance than "regular" Result<T, E>. (Might be nice to mention this on the corresponding lobste.rs thread as well to see if anyone has anything interesting to add, if anyone has access) [0]: https://github.com/iex-rs/iex