Rust in Action
FREE
You can see any available part of this book for free.Click the table of contents to start reading.
The easiest way to learn Rust I've ever seen!
Rust in Action introduces the Rust programming language by exploring numerous systems programming concepts and techniques.You'll be learning Rust by delving into how computers work under the hood. You'll find yourself playing with persistent storage, memory, networking and even tinkering with CPU instructions. The book takes you through using Rust to extend other applications and teaches you tricks to write blindingly fast code. You'll also discover parallel and concurrent programming. Filled to the brim with real-life use-cases and scenarios, you'll go beyond the Rust syntax and see what Rust has to offer in real-world use cases.
Table of Contents takes you straight to the bookdetailed table of contents
1 Introducing Rust
1.1 How is Rust used?
1.2 What is it like to advocate for Rust at work?
1.3 What does Rust look and feel like?
1.4 What is Rust?
1.4.1 Safety
1.4.2 Productivity
1.4.3 Control
1.5 Rust’s Big Features
1.5.1 Performance
1.5.2 Concurrency
1.5.3 Memory Efficiency
1.6 Downsides of Rust
1.6.1 Compile Times
1.6.2 Strictness
1.6.3 Size of the Language
1.6.4 Hype
1.7 Where does Rust fit best?
1.7.1 Data Processing
1.7.2 Extending an Application
1.7.3 Operating in Resource-constrained Environments
1.7.4 Applications
1.7.5 Systems Programming
1.8 Rust’s hidden feature: its community
1.9 A Taste of the Language
1.9.1 Cheating Your Way To "Hello, world!"
1.9.2 Your First Rust Program
1.10 Rust phrase book
1.11 Summary
Part 1: What Makes Rust Distinctive?
2 Language Foundations
2.1 A Glance at Rust’s Syntax
2.2 A whole program with main()
2.3 Starting out With Numbers
2.4 Type-aware control flow with match
2.5 Getting Stuff Done With Functions
2.5.1 Advanced Function Definitions
2.6 Creating grep-lite v1
2.7 Making Lists of Things with Arrays, Slices and Vectors
2.7.1 Arrays
2.7.2 Slices
2.7.3 Vectors
2.8 Including Third Party Code
2.8.1 Adding Support for Regular Expressions
2.8.2 Generating Crates' Documentation Locally
2.8.3 Managing Rust toolchains with rustup
2.9 Supporting Command Line Arguments
2.10 Reading From Files
2.11 Reading from STDIN
2.12 Summary
3 Compound Data Types
3.1 Using plain functions to experiment with an API
3.2 Modeling Files With struct
3.3 Adding Methods to a struct with impl
3.3.1 Simplifying object creation by implementing a new() method
3.4 Returning errors
3.4.1 Modifying a known global variable
3.4.2 Making use of the Result return type
3.5 Defining and making use of enum
3.5.1 Using an enum to manage internal state
3.6 Defining Common Behavior with Traits
3.6.1 Creating a Read trait
3.6.2 Implementing Display for your own types
3.7 Exposing your types to the world
3.7.1 Protecting private data
3.8 Creating In-line Documentation
3.8.1 Using rustdoc to Render Docs For a Single Source File
3.8.2 Using carg to Render Docs for a Crate and its Dependencies
3.9 Summary
4 Lifetimes, Ownership and Borrowing
4.1 “Implementing” a Mock CubeSat Ground Station
4.1.1 Encountering our first lifetime issue
4.1.2 Special behavior of primitive types
4.2 Guide to the figures in this chapter
4.3 What is an Owner? Does it Have any Responsibilities?
4.4 How Ownership Moves
4.5 Resolving Ownership Issues
4.5.1 Use references where full ownership is not required
4.5.2 Use Fewer Long-Lived Values
4.5.3 Duplicate the value
4.5.4 Wrap Data Within Specialty Types
4.6 Summary
Part 2: Demystifying Systems Programming
5 Data in Depth
5.1 Bit Patterns and Types
5.2 Life of an integer
5.2.1 Understanding Endianness
5.3 Decimal Numbers
5.3.1 About Floating Point
5.3.2 Looking inside an f32
5.3.3 Representing decimal numbers in a single byte with a fixed-point number format
5.4 Generating f32 values between 0 and 1 from random bytes
5.5 Implementing a CPU in Software to Establish that Functions are also Data
5.5.1 CPU 1: “the Adder”
5.5.2 First working emulator
5.5.3 CPU 2: “the Multi-Adder”
5.5.4 CPU 3: Adding functions
5.5.5 CPU 4: Adding the rest
5.6 Summary
6 Memory
6.1 Pointers
6.2 Exploring Rust’s reference and pointer types
6.2.1 Raw pointers in Rust
6.2.2 Rust’s pointer ecosystem
6.2.3 Smart pointer building blocks
6.3 Providing programs with memory for their data
6.3.1 The stack
6.3.2 The heap
6.3.3 What is dynamic memory allocation?
6.4 Virtual Memory
6.4.1 Background
6.4.2 Step 1: Having a Process Scan Its Own Memory
6.4.3 Translating virtual addresses to physical addresses
6.4.4 Step 2: Working with the operating system to scan an address space
6.4.5 Step 3: reading and writing bytes to processes' memory
6.5 Wrap up
7 Files & Storage
7.1 What is a file format?
7.2 Creating your own file formats for data storage with serde
7.2.1 Writing data to disk with serde & the bincode format
7.3 Implementing a hexdump Clone
7.4 File operations in Rust
7.4.1 Opening a file in Rust and controlling its file mode
7.4.2 Interacting with the file system in a type-safe manner with std::fs::Path
7.5 Implementing a key-value store with a log-structured, append-only storage architecture
7.5.1 The key-value model
7.5.2 Introducing actionkv v0.1: an in-memory key-value store with a command line interface
7.6 actionkv v0.1 front-end code
7.6.1 Tailoring what is compiled with conditional compilation
7.7 Understanding the core of actionkv: the libactionkv crate
7.7.1 Initializing the ActionKV struct
7.7.2 Processing an individual record
7.7.3 Writing multi-byte binary data to disk in a guaranteed byte order
7.7.4 Validating I/O errors with checksums
7.7.5 Inserting a new key-value pair into an existing database
7.7.6 libactionkv full code listing
7.7.7 Working with keys and values with HashMap and BTreeMap
7.7.8 Creating a HashMap and populating it with values
7.7.9 Retrieving values from HashMap and BTreeMap
7.7.10 How to decide between HashMap and BTreeMap
7.7.11 Adding database index to action_kv v0.2
7.8 Summary
8 Networking
8.1 Just enough HTTP
8.2 Generating an HTTP GET request with reqwest
8.3 Trait Objects
8.4 TCP
8.4.1 What is a “port number”?
8.4.2 Converting a hostname to an IP address
8.5 Ergonomic Error Handling for Libraries
8.5.1 Issue: unable to return multiple error types
8.5.2 Wrapping downstream errors by defining our own error type
8.5.3 Cheat with unwrap() and expect()
8.6 MAC addresses
8.6.1 Generating MAC addresses
8.7 Implementing state machines with Rust’s enums
8.8 Raw TCP
8.9 Creating a virtual networking device
8.10 “Raw” HTTP
8.11 Wrapping Up
9 Time and Time Keeping
9.1 Background
9.2 Sources of Time
9.3 Definitions
9.4 Encoding Time
9.4.1 Representing time zones
9.5 clock v0.1.0: Teaching an application how to tell the time
9.6 clock v0.1.1: Formatting timestamps to comply with ISO 8601 and email standards
9.6.1 Refactoring the clock v0.1.0 code to support wider architecture
9.6.2 Formatting the time as a UNIX timestamp or a formatted string according to ISO 8601, RFC 2822, and RFC 3339
9.6.3 Providing a full command-line interface
9.6.4 The full clock v0.1.1 code listing
9.7 clock v0.1.2: Setting the time
9.7.1 Common behavior
9.7.2 Setting the time in operating systems that use libc
9.7.3 Setting the time on MS Windows
9.7.4 clock v0.1.2 Full code listing
9.8 Improving error handling
9.9 clock v0.1.3 Resolving differences between clocks with the Network Time Protocol (NTP)
9.9.1 Sending NTP requests and interpreting responses
9.9.2 Adjusting the local time as a result of the server’s response
9.9.3 Converting between time representations that use different precisions and epochs
9.9.4 clock v0.1.3 full code listing
9.10 Summary
10 Threads, Processes & Containers
11 Kernel
12 Signals, Interrupts and Exceptions
12.1 Disambiguating several related terms
12.2 Avoiding writing code by relying on the default signal handling behavior
12.2.1 Using SIGSTOP and SIGCONT to suspend and resume a program’s operation
12.2.2 Listing all signals supported by the operating system
12.3 Handling signals with custom actions
12.3.1 Global variables in Rust
12.3.2 Using a global variable to indicate that shutdown has been initiated
12.4 Sending application-defined signals
12.4.1 Understanding function pointers and their syntax
12.5 Ignoring signals
12.6 Shutting down from deeply nested call stacks
12.6.1 Setting up intrinsics in a program
12.6.2 Casting a pointer to another type
12.6.3 Running the Linux-specific code from Listing 12.23 in other operating systems via Docker
12.6.4 Compiling the code
12.7 A note on applying these techniques to platforms without signals
12.8 Revising exceptions
12.9 Summary
About the Technology
Rust is a new systems programming language that gives you the low-level power of C with the elegance and ease of languages like Ruby and Python. Rust is thread safe, enabling "fearless concurrency". Threads are guaranteed not to overwrite each others' data, but it doesn't impose a garbage collector on you, keeping runtime performance predictable. It incorporates features from functional programming such as higher-order functions that allow for compact, readable programs. Rust is perfect for developers who want to fearlessly explore systems programming with a more ergonomic, less intimidating alternative to C or C++.What's inside
- Portability with Rust
- Concurrent and parallel programming
- Sharing resources with locks or atomic operations
- Avoiding programming with global state
- Message passing inside your applications
- Memory management and garbage collection
Manning Early Access Program (MEAP)
Read chapters as they are written, get the finished eBook as soon as it’s ready, and receive the pBook long before it's in bookstores.
- customers also bought these items
- Functional Programming in C++
- Rust in Motion
- Get Programming with Haskell
- WebAssembly in Action
- Secure by Design
- C++ Concurrency in Action, Second Edition
- customers also bought these items
- Elixir in Action, Second Edition
- Rust in Motion
- The Design of Web APIs
- Secure by Design
- WebAssembly in Action
- Microservices Patterns
Prices displayed in rupees will be charged in USD when you check out.
placing your order...
Don't refresh or navigate away from the page.FREE domestic shipping on three or more pBooks