The Rust programming language offers the rare and valuable combination of statically verified memory safety and low-level control. Imagine C++ but without dangling pointers, null pointer dereferences, leaks, or buffer overruns. With this practical guide, systems programmers will understand Rust’s rules clearly and economically. You’ll learn how to express programs that Rust can...
The Rust programming language offers the rare and valuable combination of statically verified memory safety and low-level control. Imagine C++ but without dangling pointers, null pointer dereferences, leaks, or buffer overruns. With this practical guide, systems programmers will understand Rust’s rules clearly and economically. You’ll learn how to express programs that Rust can prove are free of a broad class of common errors.
Rust brings the benefits of an expressive modern type system to systems programming. Authors Jim Blandy and Jason Orendorff demonstrate how Rust’s features put programmers in control over memory consumption and processor use, combining predictable performance with memory safety and trustworthy concurrency.
You’ll learn:
How to write fast, safe, concurrent programs in Rust
Rust’s rules for managing memory efficiently, including ownership, borrowing, moves, and lifetimes
How to design interfaces that fit well into the Rust ecosystem
Rust’s all-purpose Cargo tool for building, testing, and managing Rust packages
High-level features like traits, generics, closures, and iterators that make Rust productive and flexible
You've heard that Rust lets you write safe, fase, concurrent programs. This is the chapter where we show you how it's done. We'll cover three ways to use Rust threads:
1. Fork-join parallelism
2. Channels
3. Shared muatble state (查看原文)
A panic is not a crash. It’s not undefined behavior. It’s more like a RuntimeException in Java or a std::logic_error in C++. The behavior is well-defined; it just shouldn’t be happening.
Panic is safe. It doesn’t violate any of Rust’s safety rules; even if you manage to panic in the middle of a standard library method, it will never leave a dangling pointer or a half-initialized value in memory. The idea is that Rust catches the invalid array access, or whatever it is, before anything bad happens. It would be unsafe to proceed, so Rust unwinds the stack. But the rest of the process can continue running.
Panic is per thread. One thread can be panicking while other threads are going on about their normal business. In Chapter19, we’ll show how a parent thread can find out when a child threa... (查看原文)
书写得不错，但是推荐看第二版，因为很多用法已经和旧版有区别。例如第11章特型的例子，这版里是 use std::io::Write; let mut buf: Vec<u8> = vec![]; let writer: &mut Write = &mut buf; 而第二版里是 use std::io::Write; let mut buf: Vec<u8> = vec![]; let writer: &mut...
(展开)
3 有用 pluskid 2022-01-30 05:38:28
比 The Rust Programming Language 要更进阶一些的书，内容组织方式也比简单罗列所有语言特性稍微更有趣一点，对于已经有其他编程经验的读者更友好一些。
8 有用 et 2021-12-24 19:42:14
如果 Rust 的书只看一本的话，我选这本（2021）
0 有用 cppcoffee 2021-07-15 14:20:31
读了不下4本rust书籍，如果让我推荐一本rust书，那么我会推荐这本。比官方的还要详细，还要深入。
0 有用 _浮生若梦 2023-01-03 14:00:09 上海
就目前参考的各种 Rust 资料来看，这本书是我心目中绝对的第一，值得放手边作为参考书的程度👀
2 有用 赵龙 2022-10-10 14:16:44 北京
读完官方那本之后，推荐读一下这本。好多概念看完这本后能加深理解，醍醐灌顶。本书配图非常棒，所有权、内存布局等概念，一图胜千言