Edit: This list is now maintained in the rust-anthology repo.
- Introduction
- Ownership
- Where Rust Really Shines
- Rust Means Never Having to Close a Socket
- The Problem with Single-threaded Shared Mutability
- Rust Ownership the Hard Way
- Strategies for Solving "cannot move out of" Borrowing Errors
- Interior Mutability In Rust
&
vs.ref
in Patterns- Holy
std::borrow::Cow
- Graphical Depiction of Ownership and Borrowing in Rust
- Wrapper Types in Rust: Choosing Your Guarantees
- Concurrency
- Traits
- Macros
- The Rust Language
unsafe
Rust- Unsafe Rust: An Intro and Open Questions
- What Does Rust's
unsafe
Mean? - Memory Leaks are Memory Safe
- On Reference Counting and Leaks
- A Few More Remarks on Reference Counting and Leaks
- Pre-pooping Your Pants With Rust
- Niko's Unsafe Abstractions Series
- How MutexGuard was Sync When It Should Not Have Been
- The Scope of Unsafe
- Rust in Practice
- The Many Kinds of Code Reuse in Rust
- Rust Error Handling
- Why your first FizzBuzz implementation may not work
- Herman Radtke's
String
Trilogy - Gankro's Collections Trilogy
- Learning Rust with Entirely Too Many Linked Lists
- Working With C Unions in Rust FFI
- Quick tip: the
#[cfg_attr]
attribute - Using the
Option
Type Effectively - Rust + Nix = Easier Unix Systems Programming
- ripgrep code review
- Elegant Library APIs in Rust
- gnome-class: Integrating Rust and the GNOME object system
- Making Terminal Applications in Rust with Termion
- Exploring Rust's standard library: system calls and errors
- Starting a New Rust Project Right, with error-chain
- Async I/O
- Performance
- Benchmarking In Rust
- Profiling Rust Applications on Linux
- Does Your Code Leave a Trail of Slowness?
- Rust Faster!
- Rust Performance: A story featuring perf and flamegraph on Linux
- Zero-cost abstractions
- ripgrep is faster than {grep, ag, git grep, ucg, pt, sift}
- Rust Performance Pitfalls
- Optimizing
Rc
Memory Usage in Rust
- The Rust Toolbox
- Internals
- Culture
- Stability as a Deliverable
- The Not Rocket Science Rule of Software Engineering
- RIIR
- Making Your Open Source Project Newcomer Friendly
- Rust Discovery, or: How I Figure Things Out
- The Minimally-nice Open Source Software Maintainer
- Fireflowers
- Rust is More than Safety
- Rust is Mostly Safety
- Safety is Rust's Fireflower
- Fire Mario, Not Fire Flowers
- Fire Flowers and Marios
- Rust is About Productivity
- Rust is Its Community
- My Thoughts on Rust in 2017
- Rust is Software's Salvation
- Rust is My Magic Whistle
- Rust is Something Old Made New
- Rust is Needed Now More than Ever
- Rust is About Boldness
- Rust is About Better Citizenship
- Rust Marketing Pitch
- Cheat Sheets
- Additional Reading
- Uncategorized Chapters
- Why Is A Rust Executable Large?
- Where Are You
From::from
? - Type-level Shenanigans
- Rustic Bits
- Mapping Over Arrays
- Rust for Functional Programmers
- From &str to Cow
- Graydon's Lists
- for loops in Rust
- Convenient and Idiomatic Conversions in Rust
- Using and_then and map combinators on the Rust Result Type
- I used to use pointers. Now what?
- Let’s Stop Ascribing Meaning to Code Points
- What are Sum, Product, and Pi types?
- Rust your ARM microcontroller!
- It's Time for a Memory Safety Intervention
- Bugs You'll Probably Only Have in Rust
- Four Years With Rust
- My Experience Writing Enjarify in Rust
- Rust's Type System is Turing-Complete
- Rust Makes Invariants Explicit
- Rust: A Scala Engineer's Perspective