Book Image

Rust Quick Start Guide

By : Daniel Arbuckle
Book Image

Rust Quick Start Guide

By: Daniel Arbuckle

Overview of this book

Rust is an emerging programming language applicable to areas such as embedded programming, network programming, system programming, and web development. This book will take you from the basics of Rust to a point where your code compiles and does what you intend it to do! This book starts with an introduction to Rust and how to get set for programming, including the rustup and cargo tools for managing a Rust installation and development work?ow. Then you'll learn about the fundamentals of structuring a Rust program, such as functions, mutability, data structures, implementing behavior for types, and many more. You will also learn about concepts that Rust handles differently from most other languages. After understanding the Basics of Rust programming, you will learn about the core ideas, such as variable ownership, scope, lifetime, and borrowing. After these key ideas, you will explore making decisions in Rust based on data types by learning about match and if let expressions. After that, you'll work with different data types in Rust, and learn about memory management and smart pointers.
Table of Contents (10 chapters)

The lifetime of borrowed data

Borrows can not last longer than the data value that they're borrowing. The Rust compiler has to make sure that no part of the program could allow that to happen, which means that it has to keep track of the lifetime of every borrow. In the examples we've seen so far, that's easy, because each borrow was created when we called a function and ended when the function returned, while the values that were borrowed lived until the end of the block expression that contained the function calls.

The lifetimes of the borrows were obviously shorter than the lifetimes of the variables, beginning later and ending sooner.

However, it's not hard to create situations where the compiler needs us to give it a hint about how long a borrow can exist, or how long the borrowed value will remain valid. We've already seen that once, when we used...