To get the most out of this book

1. We assume familiarity with the concepts from the first 10 chapters of Rust documentation (https://doc.rust-lang.org/book/). Some of the material from these chapters is fairly advanced, so we will also explain that here when relevant. However, the knowledge of syntax and very basic features will be expected.
2. Clone the GitHub code repository and follow along. Tweak the examples and see what effects you can create.
3. Stay curious. Some of the keywords we mentioned could fill an entire book with unique content. Some of these topics presented are so pervasive that they have decent Wikipedia articles to explain and expand on the concepts. However, knowing the keyword is required to even know what to search for.

Download the example code files

You can download the example code files for this book from your account at www.packtpub.com. If you purchased this book elsewhere, you can visit www.packtpub.com/support and register to have the files emailed directly to you.

You can download the code files by following these steps:

1. Log in or register at www.packtpub.com.
2. Select the SUPPORT tab.
3. Click on Code Downloads & Errata.
4. Enter the name of the book in the Search box and follow the onscreen instructions.

Once the file is downloaded, please make sure that you unzip or extract the folder using the latest version of:

• WinRAR/7-Zip for Windows
• Zipeg/iZip/UnRarX for Mac
• 7-Zip/PeaZip for Linux

The code bundle for the book is also hosted on GitHub at https://github.com/PacktPublishing/Hands-On-Functional-Programming-in-Rust. In case there's an update to the code, it will be updated on the existing GitHub repository.

We also have other code bundles from our rich catalog of books and videos available at https://github.com/PacktPublishing/. Check them out!

Conventions used

There are a number of text conventions used throughout this book.

CodeInText: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: "Let's start by defining some of the type declarations for the physics module."

A block of code is set as follows:

pub trait MotorController
{
   fn init(&mut self, esp: ElevatorSpecification, est: ElevatorState);
   fn poll(&mut self, est: ElevatorState, dst: u64) -> MotorInput;
}

Any command-line input or output is written as follows:

closure may outlive the current function, but it borrows `a`, which is
owned by the current function

Bold: Indicates a new term, an important word, or words that you see onscreen.

Warnings or important notes appear like this.

Tips and tricks appear like this.