A common belief is that unknown error (i.e. developer, non-operational) can leave an app in an inconsistent state thus we better let the process exit. Can you provide an example of such a error?For example, should my code tries to fetch some remote data which is not available now- it's obviously operational error without any side effects which shouldn't lead to process exit. I'm looking for the opposite case - an error that has does leave the process in faulty state
Submitted January 02, 2018 at 03:53PM by yonatannn
No comments:
Post a Comment