Catching Errors

[Jacob Carlborg via Digitalmars-d]

On 2017-01-20 03:11, Adam D. Ruppe wrote:

> It is just that Errors are not necessarily *thrown*. The implementation
> is allowed to immediately abort on them too - your catch has no
> guarantee to actually run, whereas with Exceptions, they are.

That doesn't work well with a unit test framework that want to catch 
assertions to be able to continue with other tests.

-- 
/Jacob Carlborg