Book Overview & Buying
Table Of Contents

Rust Programming By Example

By : Gomez, Antoni Boucher

3.5 (4)

Buy this Book

Rust Programming By Example

3.5 (4)

By: Gomez, Antoni Boucher

Buy this Book

Overview of this book

Rust is an open source, safe, concurrent, practical language created by Mozilla. It runs blazingly fast, prevents segfaults, and guarantees safety. This book gets you started with essential software development by guiding you through the different aspects of Rust programming. With this approach, you can bridge the gap between learning and implementing immediately. Beginning with an introduction to Rust, you’ll learn the basic aspects such as its syntax, data types, functions, generics, control flows, and more. After this, you’ll jump straight into building your first project, a Tetris game. Next you’ll build a graphical music player and work with fast, reliable networking software using Tokio, the scalable and productive asynchronous IO Rust library. Over the course of this book, you’ll explore various features of Rust Programming including its SDL features, event loop, File I/O, and the famous GTK+ widget toolkit. Through these projects, you’ll see how well Rust performs in terms of concurrency—including parallelism, reliability, improved performance, generics, macros, and thread safety. We’ll also cover some asynchronous and reactive programming aspects of Rust. By the end of the book, you’ll be comfortable building various real-world applications in Rust.

Preface

Who this book is for

What this book covers

To get the most out of this book

Get in touch

Free Chapter

Basics of Rust

Getting to know Rust

Documentation and reference

Main function

Built-in data types

Control flow

Creating functions

Creating structures

References

Methods

Tuples

Enumerations

Pattern matching

Traits

Generics

Arrays

Macros

Summary

Starting with SDL

Understanding Rust crates

Installing SDL2

Setting up your Rust project

Rust's modules

Tetris

Creating a window

Drawing

Handling files

Summary

Events and Basic Game Mechanisms

Writing Tetris

Summary

Adding All Game Mechanisms

Getting started with game mechanisms

Summary

Creating a Music Player

Installing the prerequisite

Creating your first window

Creating a toolbar

Improving the organization of the application

Adding tool button events

Containers

Adding a playlist

Opening MP3 files

Summary

Implementing the Engine of the Music Player

Installing the dependencies

Decoding MP3 files

Playing music

Pausing and resuming the song

Showing the progression of the song

Improving CPU usage

Showing the song's current time

Loading and saving the playlist

Using gstreamer for playback

Summary

Music Player in a More Rusty Way with Relm

Reasons to use relm instead of gtk-rs directly

Creating a window with relm

Widget

Adding child widgets

Playlist

Adding a relm widget

Communicating between widgets

Playing music

Computing the song duration

Using relm on stable Rust

Relm widgets data binding

Summary

Understanding FTP

File transfer protocol

Summary

Implementing an Asynchronous FTP Server

Advantages of asynchronous IO

Disadvantages of asynchronous IO

Creating the new project

Using Tokio

Using futures

Handling errors

Starting the Tokio event loop

Starting the server

Handling commands

Managing the current working directory

Setting the transfer type

Entering passive mode

Quitting

Creating directories

Removing directories

Summary

Implementing Asynchronous File Transfer

Listing files

Downloading a file

Uploading files

Going further!

Unit tests

Integration tests

Documentation

Documentation tests

Fuzzing tests

Summary

Rust Best Practices

Rust best practices

Summary

Other Books You May Enjoy

Leave a review - let other readers know what you think

Writing Tetris

First, let's review the Tetris rules (just in case):

There is a grid with a height of 16 blocks and a width of 10 blocks.
You have seven different tetrimino (a tetris piece) that are all composed of four blocks.
A new tetrimino appears at the top of the game's grid every time the previous one cannot descend any more (because the block below is already occupied or because you've reached the game's floor).
The game is over when a new tetrimino cannot appear anymore (because there is already a tetrimino at the top of the grid).
Every time a line is full (all blocks are occupied by a tetrimino part), it disappears and all lines above descend by one line.

Now that we all agree on the game rules, let's see how to actually write those mechanisms.

First, we need to actually create those tetriminos.

...

Tech Concepts

Programming languages

Tech Tools