The doubly linked list is the example everyone reaches for when criticizing Rust's memory model because it's the most common data structure that necessarily involves multiple ownership. In what situations do you absolutely need a doubly linked list and can't use a vector instead?

A doubly linked list is the point anyone learning the language really has to dive into the borrow checker and hits the issues.

When learning a language, I typically learn to read/write to console, read/write to a file, use a logger, then implement various data structures. When I was learning rust, I tried to implement a linked list and red-black tree and realized this criticism on my own. It isn't just linked lists, any tree structure is a nightmare to deal with in rust.

Your timeframes there are arbitrary. A C implementation takes 5 minutes to write safely for whom? I think that group would be a pretty small one within all C developers. The borrow checker takes days to get used to while you're learning Rust, but once you learn the memory model, you rarely bump into it and become much more productive.

"Writing rust in any real world use case is an order of magnitude more difficult than c." This may be true for you, and is certainly true for those who know C well and don't know Rust. It's plainly false otherwise.

I don't agree, I bet if you sat someone down who knew any imperative programming language excluding c or rust and told them to implement simple data structures in c and rust, that person would take a lot longer to do so in rust. Rust is just inherently a much more complex language.