Will your users be happier to get an assertion failure when they run your code, ... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		dbdr 89 days ago \| parent \| context \| favorite \| on: Three ways formally verified code can go wrong in ... 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)

0xDEAFBEAD 89 days ago [–]

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.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact