Hacker News Reader

In addition to avoiding undefined behavior, MISRA discourages language features that are "dangerous" like I/O and dynamic memory routines. It also defines some (controversial) styling rules, such as requiring functions to have exactly one exit point.

View on HN

SE/SE is called out explicitly in the ISO26262 documents (functional safety in road vehicles). This makes it easy to defend the inclusion of such a guideline, even if you may not agree with it.

But as it happens, MISRA C++:2023 doesn't have this guideline.

no_std rust then which has no i/o or heap, and what misra rules would there even need to be?

Code styling rules, such as requiring functions to have exactly one exit point, could be carried over to Rust. Many existing rules are still relevant for unsafe blocks and there would likely be new rules for panic.

I believe the single exit rule was dropped

Reply on news.ycombinator.com