> Only if you control the entire ecosystem, from application to every library you're ever going to use. And will not work for library code anyway. Two edge cas

> Only if you control the entire ecosystem, from application to every library you're ever going to use. And will not work for library code anyway. Two edge cases existing is a terrible argument for creating a world in which any possible edge case must also be accounted for. >> This is a terrible argument for treating all code as potentially failing with any possible error condition. > This is reality. Some programs can ignore it, hand-waving possibilities out, expecting that it won't happen and it's not your problem. That's one approach, I guess. No, it’s not reality. It’s the mess you create when you work in languages with untyped exception handling and with people that insist on writing code the way you suggest.