too-many-lists VS book

Compare too-many-lists vs book and see what are their differences.

SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
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
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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

Posts with mentions or reviews of too-many-lists. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2026-05-24.
  • Migrating from Go to Rust
    7 projects | news.ycombinator.com | 24 May 2026
  • Learn Rust with Too Many Linked Lists
    1 project | news.ycombinator.com | 22 Apr 2026
  • Learning Rust with Too Many Linked Lists
    1 project | news.ycombinator.com | 7 Mar 2026
  • Show HN: Iron-Wolf – Wolfenstein 3D source port in Rust
    7 projects | news.ycombinator.com | 21 Feb 2026
    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
    2 projects | news.ycombinator.com | 8 Jan 2026
    > 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
    2 projects | news.ycombinator.com | 11 Nov 2025
    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
    4 projects | news.ycombinator.com | 3 Oct 2025
    Have you read https://rust-unofficial.github.io/too-many-lists/?
  • What Is a Weak Pointer in Rust (and Why It Matters)?
    1 project | dev.to | 22 Sep 2025
    Too Many Lists - A fantastic deep dive into implementing various list types in Rust
  • Rust for Beginners: 8 Practical Tips to Get Started
    1 project | dev.to | 2 Sep 2025
    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++)
    14 projects | news.ycombinator.com | 6 May 2025
    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

Posts with mentions or reviews of book. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2026-05-24.

What are some alternatives?

When comparing too-many-lists and book you can also consider the following projects:

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

SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured

Did you know that Rust is
the 3rd most popular programming language
based on number of references?