awesome-rust-mentors VS nomicon

Above all, don't be afraid to ask for help. Ask questions on /r/learnrust. Check out Awesome Rust Mentors and see if it's something you'd be interested in. Find a local user group or Uni or whatever that has experienced Rust programmers and try to make friends there. You're at the stage where asking questions is often the fast path.

The API guidelines will help you write nice APIs. Clippy will usually at least find some things, try running with -Wclippy::pedantic for a lot more messages. Also you can ask mentors for specific guidance. Hope that helps.

You really need to find a mentor for this project. May I suggest Awesome Rust Mentors https://rustbeginners.github.io/awesome-rust-mentors/ ?

Maybe try https://rustbeginners.github.io/awesome-rust-mentors/ ?

I'm a pretty highly motivated high school student and I've started doing projects and learning theory that would significantly benefit from mentorship to clarify things/answer obscure technical questions. Where can I look for someone that might be willing to help me out?

Shoutout to [rust mentors](https://github.com/RustBeginners/awesome-rust-mentors) for doing something similar but I'm looking for a more general site or social scene where people volunteer their time (ideally with an opportunity to give back and mentor someone else so I don't feel guilty)

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.