Book Image

Creative Projects for Rust Programmers

By : Carlo Milanesi
Book Image

Creative Projects for Rust Programmers

By: Carlo Milanesi

Overview of this book

Rust is a community-built language that solves pain points present in many other languages, thus improving performance and safety. In this book, you will explore the latest features of Rust by building robust applications across different domains and platforms. The book gets you up and running with high-quality open source libraries and frameworks available in the Rust ecosystem that can help you to develop efficient applications with Rust. You'll learn how to build projects in domains such as data access, RESTful web services, web applications, 2D games for web and desktop, interpreters and compilers, emulators, and Linux Kernel modules. For each of these application types, you'll use frameworks such as Actix, Tera, Yew, Quicksilver, ggez, and nom. This book will not only help you to build on your knowledge of Rust but also help you to choose an appropriate framework for building your project. By the end of this Rust book, you will have learned how to build fast and safe applications with Rust and have the real-world experience you need to advance in your career.

Related Content you might be interested in

Current Title:

Small book image
Creative Projects for Rust Programmers
Carlo Milanesi
Jun, 2020 | 404 pages
Small book image
Mastering Rust
Vesa Kaihlavirta
May, 2017 | 354 pages
Small book image
Practical System Programming for Rust Developers
Prabhu Eshwarla
Dec, 2020 | 388 pages
Small book image
Hands-On Microservices with Rust
Denis Kolodin
Jan, 2019 | 520 pages
Table of Contents (14 chapters)
Preface
Preface
Who this book is for
What this book covers
To get the most out of this book
Get in touch
1
Rust 2018: Productivity
Rust 2018: Productivity
Technical requirements
Understanding the different editions of Rust
The projects
Working through the examples in this book
Exploring some utility crates
Summary
Questions
Free Chapter
2
Storing and Retrieving Data
Storing and Retrieving Data
Technical requirements
Project overview
Reading a TOML file
Reading and writing a JSON file
Reading an XML file
Accessing databases
Accessing a SQLite database
Accessing a PostgreSQL database
Storing and retrieving data from a Redis store
Putting it all together
Summary
Questions
3
Creating a REST Web Service
Creating a REST Web Service
Technical requirements
The REST architecture
Project overview
Essential background theory and context
Building a stub of a REST web service
Building a complete web service
Building a stateful server
Returning JSON data
Summary
Questions
Further reading
4
Creating a Full Server-Side Web App
Creating a Full Server-Side Web App
Technical requirements
Definition of a web app
Understanding the behavior of a web app
Project overview
Using the Tera template engine
A simple list of persons
A CRUD application
Handling an application with authentication
Summary
Questions
Further reading
5
Creating a Client-Side WebAssembly App Using Yew
Creating a Client-Side WebAssembly App Using Yew
Technical requirements
Introducing Wasm
Understanding the MVC architectural pattern
Project overview
The incr app
The adder app
The login app
The yauth app
A web app accessing a RESTful service
Summary
Questions
Further reading
6
Creating a WebAssembly Game Using Quicksilver
Creating a WebAssembly Game Using Quicksilver
Technical requirements
Project overview
Understanding the animation loop architecture
Implementing the ski project
Implementing the silent_slalom project
Implementing the assets_slalom project
Summary
Questions
Further reading
7
Creating a Desktop Two-Dimensional Game Using ggez
Creating a Desktop Two-Dimensional Game Using ggez
Technical requirements
Project overview
Understanding linear algebra
Implementing the gg_ski project
Implementing the gg_silent_slalom project
Implementing the gg_assets_slalom project
Implementing the gg_whac project
Summary
Questions
Further reading
8
Using a Parser Combinator for Interpreting and Compiling
Using a Parser Combinator for Interpreting and Compiling
Technical requirements
Project overview
Introducing Calc
Understanding formal languages and their parsers
Using Nom to build parsers
The calc_parser project
The calc_analyzer project
The calc_interpreter project
The calc_compiler project
Summary
Questions
Further reading
9
Creating a Computer Emulator Using Nom
Creating a Computer Emulator Using Nom
Technical requirements
Project overview
Introducing a very simple machine language
Defining a byte-addressing machine language
The nom_byte_machine project
The nom_disassembler project
Summary
Questions
10
Creating a Linux Kernel Module
Creating a Linux Kernel Module
Technical requirements
Project overview
Understanding kernel modules
A boilerplate module
Using global variables
Allocating memory
A character device
Summary
Questions
Further reading
11
The Future of Rust
The Future of Rust
IDEs and interactive programming
Crate maturity
Asynchronous programming
Optimization
Embedded systems
Summary
12
Assessments
Chapter 1
Chapter 2
Chapter 3
Chapter 4
Chapter 5
Chapter 6
Chapter 7
Chapter 8
Chapter 9
Chapter 10
13
Other Books You May Enjoy
Other Books You May Enjoy
Leave a review - let other readers know what you think

The nom_disassembler project

We have seen that usually, machine language programs are written in assembly language and are then translated into machine language. So, if we want to understand or debug a machine language program written by our company, we should look at the assembly language program used to generate it.

However, if this program wasn't written by our company and we don't have its assembly language source code available, it is useful to have a tool that tries its best to translate machine language programs into the corresponding assembly language programs. This tool, named a disassembler, cannot create an excellent assembly language program for the following reasons:

  • No meaningful comments can be inserted into the code.
  • Data variables have no symbolic name to make sense of them. They are just bytes of memory positions where some data is placed, and so they are referenced by their address.
  • The destinations of jumps have no symbolic names to make sense of them. They...
Previous Section
End of Section 7
Next Section