Book Image

Creative Projects for Rust Programmers

By : Carlo Milanesi
3 (1)
Book Image

Creative Projects for Rust Programmers

3 (1)
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.
Table of Contents (14 chapters)

Chapter 10

  1. It is an extension of the Linux operating system kernel that can be added or removed at runtime.
  2. The C programming language, with GCC extensions.
  3. It is a memory-only log area to which every kernel module can write. When a kernel module writes to it, a bracket-enclosed timestamp is added at the beginning of every line; this is the number of seconds and microseconds since the start of the kernel.
  1. ModInfo prints some information about a Linux module file; LsMod prints the list of all the currently loaded modules; InsMod loads a Linux module from the specified file and adds it to the running kernel; and RmMod unloads the specified module from the running Linux kernel.
  2. Because the #![no_std] directive prevents the use of the standard heap allocator and of all the standard types that use it. This directive is required as any kernel module needs a custom allocator.
  3. It is a directive to the linker to keep the exact name of the following function so that the kernel can find that...