Re-opening deprecating Option::unwrap and Result::unwrap

I write embedded code with harsh constrains. In situations like this we try to do what we can and log. In this case, we would have taken only 200 features instead of what is given, truncated basically. Then logged or triggered manual inspection of some sort. This still would have lowered the quality, but not as in original (non-rust) code. I'm telling this because just returning an error is not error handling, it is just user space unwinding.

3 Likes