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)

Higher-order functions and trait bounds that represent functions

A higher-order function is a function that takes another function, or a closure, as a parameter. In Rust, there are three somewhat unusual traits that allow us to specify a function or closure as a parameter's trait bound: Fn, FnOnce, and FnMut.

The differences between these traits are defined by what kind of variable access they permit:

  • FnOnce is the most widely applicable of these traits, because it has the fewest requirements on what types can implement it. An FnOnce only guarantees that it is safe to call it once. A function that consumes self is an example of a natural FnOnce, because having consumed self, it no longer has a self to be called on in future. Functions and closures that are safe to be called more than once still implement FnOnce, because calling them exactly once isn't an error. That...