crappylinkedlists VS book

My take is here, I learned by creating this repo: https://github.com/deavid/crappylinkedlists

I'd say it's absolutely worth learning, even if just to broaden your perspective on programming, but I might be biased :p . If you're interested, check out the Rust book: https://doc.rust-lang.org/book/

I've just started learning Rust this weekend after using Haskell for multiple years. I'm following The Rust Book and everything is pretty clear so far! Can't wait to start working on my first OSS project in Rust 🥳

What docs? Do you mean "the book", ie. https://doc.rust-lang.org/book/? If not, you should read that.

The literal entire point of the borrow checker is to stop you from doing this. You should read the book, since you obviously have not. That's the starting place.

The Rust Programming Language book is usually the first thing people recommend.

https://doc.rust-lang.org/book/

We are going to implement our language using rust, so I'll be following the standard rust project setup. If you are new to rust, please refer to the rust book which is a great resource to learn it.

After The Book, my advice is to read Learning Rust With Entirely Too Many Linked Lists, which helps to solidify your understanding of what Rust's rules mean for writing data structures, rather than using ready-made ones off crates.io.

If you haven't heard about it, reading (and implementing the projects in!) The Book is considered the canonical way to start. After that, jumping straight in may or may not work, depending on how complex the codebase is.

It took me some months to realy understand the content. Also Rust has a very good documentation see: https://doc.rust-lang.org/book/

I would second the other recommendations on this post to start with the official book (https://doc.rust-lang.org/book/). I would say reading the first ~15 chapters (+doing the exercises) would give you a good baseline from which you should be a position to start experimenting independently without constantly getting stuck (you'll still get stuck, but having read this far into the book you'll probably have a decent idea of what it is that you need to lookup to get yourself unstuck). I'd budget 2-3 days if you're quick, maybe a week if you're slower.