Abstract:The Rust programming language is increasingly being considered for safety-critical system development. However, established safety standards such as ISO 26262 require the use of coding guidelines that do not yet exist for Rust. This paper systematically examines each of the 179 MISRA C++ 2023 coding guidelines and classifies them into 6 categories based on their applicability to Rust. Our approach analyzes the rationale behind each MISRA rule to determine whether it remains valid in the Rust programming context. We find that 47.75% of the 111 as-is applicable MISRA rules are automatically enforced by Rust's language design, eliminating the need for explicit guideline enforcement. Furthermore, our analysis explicitly distinguishes between safe and unsafe Rust. We find that 69 guidelines are still relevant and still require either direct application or adaptation for Rust. Importantly, 36 of these rules are automatically satisfied when only using the safe subset of the Rust language. However, they are required again if unsafe Rust features are introduced. We also identify specific areas where new Rust-specific guidelines are needed. Where a guideline does not directly translate, we propose Rust-specific adaptations that preserve its intent. All mapping results and supporting artifacts are publicly available as open-source materials at this https URL.
| Comments: | This work has been submitted to the 45th International Conference on Computer Safety, Reliability and Security (SAFECOMP 2026) for possible publication |
| Subjects: | Software Engineering (cs.SE) |
| Cite as: | arXiv:2605.23490 [cs.SE] |
| (or arXiv:2605.23490v1 [cs.SE] for this version) | |
| https://doi.org/10.48550/arXiv.2605.23490 arXiv-issued DOI via DataCite (pending registration) |
From: Marius Molz [view email]
[v1]
Fri, 22 May 2026 10:52:52 UTC (74 KB)
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。