3 ms·
>In an embedded system such a crash may be as bad as the incorrect access itself. I don't agree on this point. An incorrect access on an embedded system has th
by foldr 4y ago
>In an embedded system such a crash may be as bad as the incorrect access itself.
I don't agree on this point. An incorrect access on an embedded system has the potential to cause all kinds of horribly subtle bugs involving memory corruption. A simple crash is generally much better.
- yaantc 4y agoPossibly, but I won't argue about hypothetical kinds of bad when a runtime issue happen ;) The point I tried to make was that you want neither for such use cases. Hence compile time verification (type base, static analysis, proofs for the most critical).