too-many-lists
book
| too-many-lists | book | |
|---|---|---|
| 232 | 671 | |
| 3,547 | 17,932 | |
| 0.0% | 1.1% | |
| 2.6 | 9.2 | |
| almost 2 years ago | about 2 months ago | |
| Rust | Rust | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
too-many-lists
- Migrating from Go to Rust
- Learn Rust with Too Many Linked Lists
- Learning Rust with Too Many Linked Lists
-
Show HN: Iron-Wolf – Wolfenstein 3D source port in Rust
I think they are likely referring to Linked lists in Rust, specifically.
See, for example:
https://rust-unofficial.github.io/too-many-lists/
https://news.ycombinator.com/item?id=22390662
-
Kernel bugs hide for 2 years on average. Some hide for 20
> It's not easier in C++. Nothing is.
The implementations of sort in Rust are filled with unsafe.[0]
Another example is that of doubly linked lists.[1] It is possible to implement a doubly linked list correctly in C++ without much trouble. In Rust, it can be significantly more challenging.
In C++, pointers are allowed to alias if their types, roughly said, are compatible. In Rust, there are stricter rules, and getting those rules wrong in an unsafe block, or code outside unsafe blocks that code inside unsafe blocks rely on, will result in breakage of memory safety.
This has been discussed by others.[2]
Based on that, do you agree that there are algorithms and data structures that are significantly easier to implement efficiently and correctly in C++ than in Rust? And thus that you are being completely wrong in your claim?
[0] https://github.com/rust-lang/rust/blob/main/library/core/src...
[1] https://rust-unofficial.github.io/too-many-lists/
[2] https://chadaustin.me/2024/10/intrusive-linked-list-in-rust/
-
Memory Safety for Skeptics
Efficiently implementing a linked list in C or C++ is easy. In Rust, less so.[0]
And the prevalence and difficulty of unsafe means both that Rust is not memory safe [1], and that Rust sometimes is less memory safe than C or C++.
[0]: https://rust-unofficial.github.io/too-many-lists/
[1]: For an example of memory unsafety in Rust: https://materialize.com/blog/rust-concurrency-bug-unbounded-...
-
Arenas in Rust
Have you read https://rust-unofficial.github.io/too-many-lists/?
-
What Is a Weak Pointer in Rust (and Why It Matters)?
Too Many Lists - A fantastic deep dive into implementing various list types in Rust
-
Rust for Beginners: 8 Practical Tips to Get Started
As soon as you get into this you need to understand borrowing and Box/Rc/Arc which you will struggle with as a beginner. Once you feel comfortable with the basics, then dive deeper into these advanced data structures. There is even a whole book about writing many flavours of linked lists: Learn Rust With Entirely Too Many Linked Lists which I'd recommend reading only after you learn at least some of the core rust pointer types.
-
Matt Godbolt sold me on Rust (by showing me C++)
The borrow checker rejects loads of sound programs - just read https://rust-unofficial.github.io/too-many-lists/
Aliasing rules can also be problematic in some circumstances (but also beneficial for compiler optimisations).
And the orphan rule is also quite restrictive for adapting imported types, if you're coming from an interpreted language.
https://loglog.games/blog/leaving-rust-gamedev/ sums up the main issues nicely tbh.
book
-
The Rust You Actually Need to Write Your First Anchor Program
And keep one tab open on the Anchor program structure page and one on the Rust book. You will not read either cover to cover. You will look up exactly the thing in front of you, which is the right way to learn a language you are using rather than studying.
-
Introduction – Rust for Python Programmers
In my experience working with newbies, the alterations Brown makes to the chapters on borrowing are strictly worse. It is very focused on ramming the difference between the stack and the heap down your throat, which has nothing to do with ownership and borrowing, and newbies will frequently say that they are extremely confused by the chapter, then sigh in relief upon reading the original version. Just use the official guide, nobody has improved upon it yet. https://doc.rust-lang.org/book
-
Deep Atlantic Storage: Rewriting in Rust
Two decades ago, I learned HTML and CSS from the official W3C specifications. While I would not go as deep as learning from the language and compiler specifications, I chose the deepest option among the three, "the book".
-
Go vs Rust: the only backend language debate that actually matters in 2026
The Rust Book the official, actually-readable Rust guide
-
CUDA-oxide: Nvidia's official Rust to CUDA compiler
Learning Rust is more alike to learning a new programming paradigm (e.g. functional when you only know imperative) than a new language with different syntax only. If you ignore that and try to jump directly to writing code more or less the same way as you used to, it will be painful. So take it slow and follow along with The Book (https://doc.rust-lang.org/book/). It all makes sense eventually and is very much worth it!
-
De C++ a Rust: cómo reescribir infraestructura crítica en producción
The Rust Programming Language (The Book) — Libro oficial gratuito, punto de partida recomendado para aprender el lenguaje.
- RUST:MY JOURNEY FROM 0 TO 1(Day 1)
-
My 2025 Tech Resolutions and My Plan for 2026
Finish again The Book. ✅
- Linux Kernel Rust Code Sees Its First CVE Vulnerability
-
Build A Watch Option for TypeScript Runtime in Rust
I read The Rust Programming Language to get a basic understanding of Rust and its tools.
What are some alternatives?
hll-rust - P2P application based on Chord algorithm (by MIT) in Rust. High-level languages: Rust - Group project (2018/2019)
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
small-ray
rust-by-example - Learn Rust with examples (Live code editor included)
patterns - A catalogue of Rust design patterns, anti-patterns and idioms
nomicon - The Dark Arts of Advanced and Unsafe Rust Programming