2 ms·
For the same reason I don't like errors in return values: most of the times you cannot recover from failure, only do some cleanup. Since you should always consi
by norswap 13y ago
For the same reason I don't like errors in return values: most of the times you cannot recover from failure, only do some cleanup. Since you should always consider than anything you call may fail and put your cleanup in a finally/defer, you don't really need checked exceptions.
Even in say, a GUI application (which you don't want to crash on failure), you'll usually contain all failures at some level and for instance display a pop-up indicating that something failed.
I suppose checked exceptions are good for recoverable failures, but I encounter preciously few of those.