An investigation into what adhering to each MISRA-C rule looks like in Rust. The intention is to decipher how much we "get for free" from the Rust compiler.
Rust
134
1 commits
updated Mar 20, 2024
The MISRA-Rust project represents an investigation into what adhering to each MISRA-C rule looks like in Rust. The intention is to decipher how much we "get for free" from the Rust compiler.
Because of the proprietary nature of the MISRA-C specificaion, the description of each rule has been omitted.
Each rule corresponds to a source file in tests/compile-fail. A "passing" test is a test that
fails to compile. Passing tests can indicate that Rust enforces a specific MISRA-C rule or that
the rule does have a Rust equivalent.
cargo test
We certainly want to hear if you think we've missed something or misrepresented a rule. Please raise an issue!
© 2018, PolySync Technologies, Inc.
Please see the LICENSE file for more details
1 commits
Rust
100.0%
An investigation into what adhering to each MISRA-C rule looks like in Rust. The intention is to decipher how much we "get for free" from the Rust compiler.
Rust
134
1 commits
updated Mar 20, 2024
The MISRA-Rust project represents an investigation into what adhering to each MISRA-C rule looks like in Rust. The intention is to decipher how much we "get for free" from the Rust compiler.
Because of the proprietary nature of the MISRA-C specificaion, the description of each rule has been omitted.
Each rule corresponds to a source file in tests/compile-fail. A "passing" test is a test that
fails to compile. Passing tests can indicate that Rust enforces a specific MISRA-C rule or that
the rule does have a Rust equivalent.
cargo test
We certainly want to hear if you think we've missed something or misrepresented a rule. Please raise an issue!
© 2018, PolySync Technologies, Inc.
Please see the LICENSE file for more details
1 commits
Rust
100.0%