This section is also available in the form of film.

1 Introduction

The purpose of this tome is for the reader to thoroughly learn the Rust programming language. This tome is also designed to act as a reference guide for more experienced Rust programmers, who’s mislaid some minor information about the language in the crazily complex mind of theirs.

Background

Rust is a general-purpose, multi-paradigm, compiled programming language which was designed with safety in mind at the same time as being both concurrent and practical. It first came around when Mozilla employee Graydon Hoare began working on it as a small pet project prior to 2009—the year Mozilla began sponsoring the project—following the language’s official announcement in 2010.

The programming language’s initial compiler was written in OCaml, but came to the point of self-compiling in the year of 2011.

This tome

If your goal is learning the Rust programming language from scratch, there’s a way in which this tome is supposed to be read in order to learn Rust as fast as possible—without putting losing the in-depth understanding at risk:

  • Start off by going over chapter one. This chapter will provide you with all the information necessary to get started on a hopefully long and journey of Rust programming with as few problems as possible.
  • Head over to chapter two, which contains in-depth information designed to learn the Rust programming language. Proceed from one section to another and stop at nothing; unless the section tells you that you’re eligible for a tutorial. Press the link taking you to the tutorial and follow the tutorial through. You’re eligible for a tutorial once you’ve acquired all necessary knowledge to go through with it—being able to understand it fully.

Tutorials are small guides for creating one specific type of program and usually are longer in length than that of the sections from chapter two. Use the tutorials to test your knowledge so that you can be sure you’ve understood everything thoroughly; also use tutorials to learn how a bigger project is supposed to be structured in Rust by convention, so that you more easily can work inside Rust projects in the future.

Moreover

There are exercises following every section. Do make sure to try them out—as they too—just like tutorials, will test your understanding on a specific matter. It’s also highly recommended that you try not to consume too much information at one time. One section a day once inside chapter two should be sufficient for beginners.

Get-go