Re:The Power of 10: Rules for Developing Safety-Critical Cod...
by hedora on Wednesday June 28, 2023 @11:44PM
(#36516066)
Rust solves the pointer escape problem via static analysis and annotations, so that’s feeling pretty dated too.
Similarly, allocation is fine with today’s large memories. You need to bound the request queue depth and the amount of memory allocated per request though.
I also question the idea that safety critical code is a special class that is distinct from normal code.
Buggy consumer devices lead to all sorts of deaths — after all, a one in a billion scenario is going to hit a few people per day on average — for example, look at the correlated 999 and 911 spam that hit iOS and (separately) android this week.
Similarly, allocation is fine with today’s large memories. You need to bound the request queue depth and the amount of memory allocated per request though.
I also question the idea that safety critical code is a special class that is distinct from normal code.
Buggy consumer devices lead to all sorts of deaths — after all, a one in a billion scenario is going to hit a few people per day on average — for example, look at the correlated 999 and 911 spam that hit iOS and (separately) android this week.