-
How to Address Functional Safety with Rust
- Chapter 1: The Rise of Rust
- Chapter 2: Functional Safety
- Chapter 3: Languages (and Language Subsets): Coding Guidelines and Rust
- Chapter 4: Fulfilling Functional Safety Requirements with Rust: A Change in Approach
- Chapter 5: The Future of Rust and Functional Safety
- Chapter 6: Reshaping Functional Safety Compliance
eBook > How to Address Functional Safety with Rust
Chapter 1: The Rise of Rust
Rust has moved from a niche systems language to a serious option for safety-critical software, because it addresses some common software hazards at the language level.
Originally created by Graydon Hoare in 2006, the early goal was for Rust to provide the low-level control of C and C++ while removing many of the risks that had become accepted as normal in systems programming. That meant building a language that could deliver code without relying on developers to manually prevent memory misuse and race conditions.
To continue reading please fill out the form below.