Comment by 0xDEAFBEAD
Comment by 0xDEAFBEAD a day ago
OK, but that's a reactor control system. If your application has no time-critical aspect, is there any good reason to prefer a proof over an assert?
Comment by 0xDEAFBEAD a day ago
OK, but that's a reactor control system. If your application has no time-critical aspect, is there any good reason to prefer a proof over an assert?
What if it's an internal tool, where correctness matters a lot, but failures matter little? E.g. roll back all database changes in case of assertion failure. Perhaps an accounting thing or something of that nature.
Will your users be happier to get an assertion failure when they run your code, compared to no error?
(the tradeoff of course being that they might get your code later because it took more time to prove the code is correct)