The Importance of Fork Safe Code in Death Testing

Death testing handles skipped sidesteps the no-accept problem but gives you a different set of problems that you don't often think about. The scalability one is why the death testing is really not viable for for many use cases like we test occasionally millions of combinations of like of negative testing and with death testing that would turn a unit test that takes you know seconds to complete to one that would take hours or just not be viable. I want to go long term with the MVP or with post MVP contract facilities which is provide a way to explicitly say return to me either a contract violation or nothing if I try to call this function with these arguments.