liveBook · Manning

Memory safety

As explained in Rust Servers, Services, and Apps

Memory safety is the property that a program cannot perform invalid accesses, use deallocated values, or otherwise violate memory-access rules.

Memory safety is one of three distinct aspects of program safety, alongside type safety and thread safety. Rust provides it without a garbage collector, helping prevent several classes of difficult memory, concurrency, and security bugs. section 1.2.2 section 1.3.2

For application backends and infrastructure services, memory safety is presented as a Rust benefit. The supplied discussion names the property but does not explain its mechanisms. section 1.2.2

How Rust Servers, Services, and Apps covers it

How deep it goes
Identifies memory safety as a distinct property but does not explain its mechanisms in the supplied discussion.
What you can do after
Evaluate Rust’s backend suitability by recognizing memory safety without a garbage collector as a way to prevent several bug classes.
How it connects
Distinguishes memory safety from type safety and thread safety, and associates Rust’s guarantees with security.

Also explained in

Compare how 3 books explain memory safety →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Rust Servers, Services, and Apps. The section links point to the parts of the book it draws on.