too-many-lists

Learn Rust by writing Entirely Too Many linked lists (by rust-unofficial)

Too-many-lists Alternatives

Similar projects and alternatives to too-many-lists

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better too-many-lists alternative or higher similarity.

too-many-lists reviews and mentions

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 2024-02-19.
  • Towards memory safety with ownership checks for C
    3 projects | news.ycombinator.com | 19 Feb 2024
    You seem to have a preset opinion, and I'm not sure you are interested in re-evaluating it. So this is not written to change your mind.

    I've developed production code in C, C++, Rust, and several other languages. And while like pretty much everything, there are situations where it's not a good fit, I find that the solutions tend to be the most robust and require the least post release debugging in Rust. That's my personal experience. It's not hard data. And yes occasionally it's annoying to please the compiler, and if there were no trait constraints or borrow rules, those instances would be easier. But way more often in my experience the compiler complained because my initial solution had problems I didn't realize before. So for me, these situations have been about going from building it the way I wanted to -> compiler tells me I didn't consider an edge case -> changing the implementation and or design to account for that edge case. Also using one example, where is Rust is notoriously hard and or un-ergonomic to use, and dismissing the entire language seems premature to me. For those that insist on learning Rust by implementing a linked list there is https://rust-unofficial.github.io/too-many-lists/.

  • Command Line Rust is a great book
    4 projects | /r/rust | 8 Dec 2023
    Advent of Code was okay until I encounterd a problem that required a graph, tree or linked list to solve, where I hit a wall. Most coding exercises are similar--those requiring arrays and hashmaps and sets are okay, but complex data structures are a PITA. (There is an online course dedicated to linked lists in Rust but I couldn't grok it either). IMO you should simply skip problems that you can't solve with your current knowledge level and move on.
  • [Media] I'm comparing writing a double-linked list in C++ vs with Rust. The Rust implementation looks substantially more complex. Is this a bad example? (URL in the caption)
    6 projects | /r/rust | 7 Dec 2023
    I feel obligated to point to the original cannon literature: https://rust-unofficial.github.io/too-many-lists/
    6 projects | /r/rust | 7 Dec 2023
    Others have mentioned "Rust with Entirely Too Many Linked Lists" already, and as the name implies it covers the subject exhaustively.
    6 projects | /r/rust | 7 Dec 2023
    you can find Learning Rust with Entirely Too Many Linked Lists over here.
    6 projects | /r/rust | 7 Dec 2023
    You really need to work through the Rust book on too many linked lists, but let me see if I can give you a quick summary.
  • Need review on my `remove()` implementation for singly linked lists
    2 projects | /r/rust | 29 Nov 2023
    I started learning Rust and like how the compiler is fussy about things. My plan was to implement the data structures I knew, but I got stuck at the singly linked list's remove() method. I've read the book as well, but I have no clue how to simplify this further:
  • Factor is faster than Zig
    11 projects | news.ycombinator.com | 10 Nov 2023
    My impression from the article is that Zig provides several different hashtables and not all of them are broken in this way.

    This reminds me of Aria's comment in her Rust tutorial https://rust-unofficial.github.io/too-many-lists/ about failing to kill LinkedList. One philosophy (and the one Rust chose) for a stdlib is that this is only where things should live when they're so commonly needed that essentially everybody needs them either directly or to talk about. So, HashTable is needed by so much otherwise unrelated software that qualifies, BloomFilter, while it's real useful for some people, not so much. Aria cleaned out Rust's set of standard library containers before Rust 1.0, trying to keep only those most people would need. LinkedList isn't a good general purpose data structure, but, it was too popular and Aria was not able to remove it.

    Having multiple hash tables feels like a win (they're optimized for different purposes) but may cost too much in terms of the necessary testing to ensure they all hit the quality you want.

  • Was Rust Worth It?
    18 projects | news.ycombinator.com | 25 Oct 2023
    > Cyclic references can be dealt with runtime safety checks too - like Rc and Weak.

    Indeed. Starting out with code sprinkled with Rc, Weak, RefCell, etc is perfectly fine and performance will probably not be worse than in any other safe languages. And if you do this, Rust is pretty close to those languages in ease of use for what are otherwise complex topics in Rust.

    A good reference for different approaches is Learn Rust With Entirely Too Many Linked Lists https://rust-unofficial.github.io/too-many-lists/

  • What are some of projects to start with for a beginner in rust but experienced in programming (ex: C++, Go, python) ?
    3 projects | /r/rust | 31 May 2023
  • A note from our sponsor - InfluxDB
    www.influxdata.com | 4 Mar 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Stats

Basic too-many-lists repo stats
219
2,961
0.0
about 2 months ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com