nomicon VS talent-plan

it’s even written by the same person that wrote the Nomicon (the guide to the dark arts of unsafe)

If you want to dive deeper you can always have other options but now there are concrete cases, if you want to do low level thing https://doc.rust-lang.org/nomicon/ while if you want multi thread/concurrency stuff https://marabos.nl/atomics/ . There are many many books so you will have to point yourself to what you want

Nonononono. SeqCst is the most error prone memory order: https://github.com/rust-lang/nomicon/issues/166

Hope this helps. For more details, see the Rustonomicon. I referenced the subtyping chapter here extensively.

Nice video! Glad I could help out. This stuff is hard, and I'm still learning a lot about it myself even years later. The Rustonomicon is a great read if you haven't already.

Have you got a moment to read through the good book , after reading through this perhaps try the Rustonomicon.

That is not what UB means. Undefined Behaviour is behaviour that the compiler is allowed to assume will never happen, and which can consequently cause miscompilations due to optimisation passes gone wrong if it does in fact occur in the source code.

It's true that Rust does not have a written specification that clearly delineates what is and isn't UB in a single place. But:

1. UB is impossible in safe code (modulo bugs in unsafe code)

2. There are resources such as the Rustinomicon (https://doc.rust-lang.org/nomicon/) that provide a detailed guide on what is and isn't allowed in unsafe code.

In practice, it's much easier to avoid UB in Rust than it is in C++.

However, this is a wide topic out of scope for a Reddit comment, so maybe just read the Rustonomicon. It explains everything about data handling in Rust.

The ownership model & borrow checker makes rust a bit of an awkward language in which to write complex data structures like trees and graphs. It can be done - since you can always use raw pointers & unsafe code when you absolutely need to to treat rust like C. But the language fights you, and the community can get a bit moralistic about this sort of thing. The rust nomicon is a fantastic resource for learning the limits of the borrow checker, and where and how to use unsafe code correctly. You will need unsafe less than you think you will, but sometimes you will have no choice.

Pls check this course: https://github.com/pingcap/talent-plan . It includes how to implement sql and key value store. It’s an awesome course

- https://hackattic.com/ : Interesting programming Problems.

- https://sadservers.com/ : Learn Linux by solving problems.

- https://fly.io/dist-sys/ : Distributed Systems Problems.

- https://github.com/pingcap/talent-plan/ : System Programming / Distributed System Challenge.

- https://protohackers.com/ : Server Programming Challenges.

- https://codecrafters.io/ : Implement server tech / softwares from scratch.

- https://hyperskill.org/ : Lots of projects based tutorials.

- https://github.com/pingcap/talent-plan/ : System Programming / Distributed System Challenge.

Awesome stuff!

Just to share in the way: open source training courses about distributed database and distributed systems by PingCap.

https://github.com/pingcap/talent-plan

You should try this lab by PingCAP (write a serde implementation for redis serialization protocol) ; you can find answers/seek help in github if you really don't know to figure out it.

I am doing pingcap's talent plan recently, where you need to implement a custom Deserializer for REdis Serialization Protocol for the building block 3. What confuses me most is the implementation of `EnumAccess` and `VariantAccess`. One of my attempt looks like the following:

Looking at your project, I would recommend following this tutorial that makes you write key-value store in Rust. They don't provide you with a solution and make you come up with most stuff yourself, but give you some direction and structure for learning. You seem to have come up with most of this yourself already, but it might still be useful for you.

If you are interested in network programming and distributed system, checkout https://github.com/pingcap/talent-plan