It's better pratice to always handle it with _or...() and in worst case, return an error using a Result<>. It's so easy that there's no legitimate reason no to.
Proper errors beat panics.
It's better pratice to always handle it with _or...() and in worst case, return an error using a Result<>. It's so easy that there's no legitimate reason no to.
Proper errors beat panics.
No replies yet.