4 ms·

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 mere

• WalterBright 8y ago
  > assertAndContinue I would never allow such a construct in any code I was in charge of.
  • laurentl 8y ago
    > assertAndContinue OTOH, it’s the perfect title for a sequel of Halt and Catch Fire.
• alangpierce 8y ago
  > this is merely an error trace, so it should just be called that 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.
  • temac 8y ago
    But is the fallback path for production even correctly tested, then? And if it is, then what becomes the point of the assertion?