On Monday, 29 September 2014 at 18:59:59 UTC, Jeremy Powers via Digitalmars-d wrote:
And this is an argument for checked exceptions - being able to explicitly state 'these are known fatal cases for this component, you should deal with them appropriately' when defining a method. Cuts down the catch/check to just the common cases, and makes such cases explicit to the caller. Anything not a checked exception falls into the 'error, abort!' path. (Memory corruption etc. being abort scenarios)
Checked exceptions are good in theory but they failed utterly in Java. I'm not interested in seeing them in D.
