rust-for-rustaceans.com VS dashmap

https://rust-for-rustaceans.com/ is meant to be a book for more advanced concepts.

RustForRustaceans has great in depth explainations of most (all?) Rust concepts. So I would pick this one once you're familiar with the basic concepts explained in thee book.

Another good piece, but I wouldn't say its for beginners, is Rust for Rustaceans by Jon Gjengset. Its definitely more intermediate topics than beginner. Still good to know about it ;)

Rust for Rusraceans

For a deeper dive into the language and stdlib, the Crust of Rust videos are great. Also, Jon's book Rust for Rustaceans is a good continuation when you've finished the official book.

Rust for rustaceons includes a decent explanation of how the whole thing works.

I love this honest, high-level take on the book. So much so that I put it in "what readers say" on rust-for-rustaceans.com. Hope you don't mind!

The problem is, every single one of these half-dozen crates has at least one known major issue (including UAF), exactly like C++ implementations (which isn't surprising since it's the kind of things where the ownership isn't clear and then the borrow checker can't help us).

Deadlocks and leaks are easy as other languages.

Have you considered https://github.com/xacrimon/dashmap ?

Dashmap made some api changes compared to the stdlibs hashmap, which leads to some oddities, as highlighted here: https://github.com/xacrimon/dashmap/issues/175

Some additional notes are in this slide deck and the implementation javadoc. You'd probably want to use something like DashMap for the hash table.

You can look at existing concurrent maps like Dashmap https://github.com/xacrimon/dashmap or Cashmap https://gitlab.redox-os.org/redox-os/chashmap

Also dashmap

The only one I've used is Dashmap, it's a concurrent interior-mutability hashmap. Very convenient crate in the case you need that.