So assertAndContinue makes no sense, right?
On my side I don't really see its point anyway. If the code is actually ready to handle such failures, this is merely an error trace, so it should just be called that.
On my side I don't really see its point anyway. If the code is actually ready to handle such failures, this is merely an error trace, so it should just be called that.
I would never allow such a construct in any code I was in charge of.
OTOH, it’s the perfect title for a sequel of Halt and Catch Fire.
It's stricter than an error trace because if it's encountered in a development/testing context, it's a hard error and the engineer must fix it to proceed. Plain error traces should only be used for expected failure scenarios (like a third-party service times out, possibly), not situations that would be considered "unexpected" to the developer.
And if it is, then what becomes the point of the assertion?